From: Mike Panetta <mpkernel@bellsouth.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Correct place for new drivers?
Date: Mon, 11 Jun 2007 09:47:45 -0400 [thread overview]
Message-ID: <1181569665.22906.13.camel@790robothead> (raw)
I want to add some I2C device drivers to my tree and I was wondering
where the correct place to put them would be so any patches I make in
future would be accepted.
I was thinking drivers/i2c (which does not exist) is that ok? I have
the Philips 2005-1 I2C demo board and I wanted to add support for some
of the devices on there which could possibly be on future devices to
control LED's or power or whatever. I am thinking about eventually
building a board around the AVR32 processor and I may use one or 2 of
these devices, so they would not be added to the tree for no reason (and
surly someone else out there uses I2C devices other then RTC's on their
boards).
I would also like to eventually add support for the Atmel board
controller on the NGW100 as soon as I figure out how it works. :)
So basically where is the best place to put a load of I2C drivers?
Thanks,
Mike Panetta
next reply other threads:[~2007-06-11 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 13:47 Mike Panetta [this message]
2007-06-11 13:59 ` [U-Boot-Users] Correct place for new drivers? Stefan Roese
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=1181569665.22906.13.camel@790robothead \
--to=mpkernel@bellsouth.net \
--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