From: Lyoo <lyoo.htp@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] What the right procedure should be when write a new driver for U-boot?
Date: Thu, 21 Sep 2006 17:00:26 +0800 [thread overview]
Message-ID: <1158829226.8962.35.camel@localhost> (raw)
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?
next reply other threads:[~2006-09-21 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 9:00 Lyoo [this message]
2006-10-05 16:01 ` [U-Boot-Users] What the right procedure should be when write a new driver for U-boot? Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2006-09-24 1:34 Lyoo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1158829226.8962.35.camel@localhost \
--to=lyoo.htp@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox