tinyx-devel Mailing List for Tinyx RTOS (Page 8)
Status: Planning
Brought to you by:
davidcohen
You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(4) |
Nov
|
Dec
(106) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
(69) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Felipe B. <fel...@us...> - 2007-10-26 19:06:10
|
Hi, On 10/26/07, David Cohen <da...@gm...> wrote: > Hi, > > Acked, but let me add something to your e-mail. So, you can comment mine > too. > This first considered platform is the Philips ARM7 LPC2148. With this > platform we have to implement: great catch! ack everything > - ISR > - startup.S (the bootloader) > - UART driver (for debug on console) > > We have also to implement some generic stuff: > - UART API > - generic console > - scheduler (just a working and simple sched.c) here I think we should really focus on the scheduler. It's probably the most important piece in our really tiny RTOS. But we should make a working one for now and really focus on the serial driver/api. > > So, we can see the Tinyx running with output console on uart. The next step > is to port a second plattform to validate our portable structure. that'll be nice... but for now we have to focus on the platform we already have but always code thinking about function pointers and callbacks > We'll use the Linux kernel to guide us most of the time, but every time with > a simpler code. probably in the near future we're gonna need to convert the lower level implementation to assembly to make the code run faster or something... but we can rely on C for now. Whenever we start adding more pieces, we think about it. > It's good to make some initial documentation for a better explanation about > the project for external users/developers. yeah... that's nice also > > BR, > > David Cohen > > > On 10/26/07, Felipe Balbi > <fel...@us...> wrote: > > > > Hi all, > > > > David, we should list here all the things we wanna do with tinyx. I > > can take the lead or putting all this information in a human-readable > > way and push it to tinyx.git TODO file. > > > > This is what I think we should be doing until Dec/31: > > > > startup.S > > kernel.c > > sched.c > > Generic ISRs (Interrupt Service Routines) > > UART Interface > > Serial "Subsystem" > > > > > > do you ack these? > > > > -- > > Best Regards, > > > > Felipe Balbi > > fel...@us... > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Tinyx-devel mailing list > > Tin...@li... > > https://lists.sourceforge.net/lists/listinfo/tinyx-devel > > > > -- Best Regards, Felipe Balbi fel...@us... |
From: David C. <da...@gm...> - 2007-10-26 18:45:42
|
Hi, Acked, but let me add something to your e-mail. So, you can comment mine too. This first considered platform is the Philips ARM7 LPC2148. With this platform we have to implement: - ISR - startup.S (the bootloader) - UART driver (for debug on console) We have also to implement some generic stuff: - UART API - generic console - scheduler (just a working and simple sched.c) So, we can see the Tinyx running with output console on uart. The next step is to port a second plattform to validate our portable structure. We'll use the Linux kernel to guide us most of the time, but every time with a simpler code. It's good to make some initial documentation for a better explanation about the project for external users/developers. BR, David Cohen On 10/26/07, Felipe Balbi <fel...@us...> wrote: > > Hi all, > > David, we should list here all the things we wanna do with tinyx. I > can take the lead or putting all this information in a human-readable > way and push it to tinyx.git TODO file. > > This is what I think we should be doing until Dec/31: > > startup.S > kernel.c > sched.c > Generic ISRs (Interrupt Service Routines) > UART Interface > Serial "Subsystem" > > > do you ack these? > > -- > Best Regards, > > Felipe Balbi > fel...@us... > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Tinyx-devel mailing list > Tin...@li... > https://lists.sourceforge.net/lists/listinfo/tinyx-devel > |
From: Felipe B. <fel...@us...> - 2007-10-26 15:47:40
|
Hi all, David, we should list here all the things we wanna do with tinyx. I can take the lead or putting all this information in a human-readable way and push it to tinyx.git TODO file. This is what I think we should be doing until Dec/31: startup.S kernel.c sched.c Generic ISRs (Interrupt Service Routines) UART Interface Serial "Subsystem" do you ack these? -- Best Regards, Felipe Balbi fel...@us... |
From: David C. <da...@gm...> - 2007-10-26 14:25:41
|
test |
From: David C. <da...@gm...> - 2007-09-28 01:44:33
|
Test |
From: David C. <da...@gm...> - 2007-09-27 19:15:14
|
Hi, This is the first test for Tinyx mailing list. BR, David |