* [U-Boot-Users] What the right procedure should be when write a new driver for U-boot?
@ 2006-09-21 9:00 Lyoo
2006-10-05 16:01 ` Wolfgang Denk
0 siblings, 1 reply; 3+ messages in thread
From: Lyoo @ 2006-09-21 9:00 UTC (permalink / raw)
To: u-boot
Hi maintainer
There is some confusion about what the right procedure should be, when
someone want to add some drivers to U-boot.
When I read U-boot's code, I found the devices initialize function
devices_init() (called in /u-boot-x.x.x/lib_xxx/board.c), It creates a
device list, then dev_xxx_init() register the devices such as LCD, USB,
Serial, Keyboard in the list.
But, some SOC have their own drivers, for example s3c24x0 have their own
driver of USB, Serial,(/cpu/arm920t/s3c24x0/usb_ohci.c) they don't care
about the device list, they do it their way.
Is there any 'official' policy on it?
^ permalink raw reply [flat|nested] 3+ messages in thread
* [U-Boot-Users] What the right procedure should be when write a new driver for U-boot?
@ 2006-09-24 1:34 Lyoo
0 siblings, 0 replies; 3+ messages in thread
From: Lyoo @ 2006-09-24 1:34 UTC (permalink / raw)
To: u-boot
Hi maintainer,
There is some confusion about what the right procedure should be, when
someone want to add some drivers to U-boot.
When I read U-boot's code, I found the devices initialize function
devices_init() (called in /u-boot-x.x.x/lib_xxx/board.c), It creates a
device list, then dev_xxx_init() register the devices such as LCD, USB,
Serial, Keyboard in the list.
But, some SOC have their own drivers, for example s3c24x0 have their own
driver of USB, Serial,(/cpu/arm920t/s3c24x0/usb_ohci.c) they don't care
about the device list, they do it their way.
Is there any 'official' policy on it?
--
Thanks & Regards
Lyoo
^ permalink raw reply [flat|nested] 3+ messages in thread
* [U-Boot-Users] What the right procedure should be when write a new driver for U-boot?
2006-09-21 9:00 Lyoo
@ 2006-10-05 16:01 ` Wolfgang Denk
0 siblings, 0 replies; 3+ messages in thread
From: Wolfgang Denk @ 2006-10-05 16:01 UTC (permalink / raw)
To: u-boot
In message <1158829226.8962.35.camel@localhost> you wrote:
>
> When I read U-boot's code, I found the devices initialize function
> devices_init() (called in /u-boot-x.x.x/lib_xxx/board.c), It creates a
> device list, then dev_xxx_init() register the devices such as LCD, USB,
> Serial, Keyboard in the list.
The "devices" list is what can be used for assignement to the
standard I/O "devices" (i. e. the stdin, stdout and stderr data
streams).
> But, some SOC have their own drivers, for example s3c24x0 have their own
> driver of USB, Serial,(/cpu/arm920t/s3c24x0/usb_ohci.c) they don't care
> about the device list, they do it their way.
Some devices like serial or LCD may be used for standard I/O streams,
others (like USB or network may not.
> Is there any 'official' policy on it?
Yes - see above.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"In matrimony, to hesitate is sometimes to be saved." - Butler
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-10-05 16:01 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-24 1:34 [U-Boot-Users] What the right procedure should be when write a new driver for U-boot? Lyoo
-- strict thread matches above, loose matches on Subject: below --
2006-09-21 9:00 Lyoo
2006-10-05 16:01 ` Wolfgang Denk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox