From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: which drivers subdirs should be automatically selected?
Date: Wed, 23 Dec 2009 10:06:39 +0100 [thread overview]
Message-ID: <20091223090639.GP15126@pengutronix.de> (raw)
In-Reply-To: <alpine.LFD.2.00.0912221000250.4427@localhost>
On Tue, Dec 22, 2009 at 10:02:40AM -0500, Robert P. J. Day wrote:
>
> drivers/Makefile:
>
> obj-y += net/
> obj-y += serial/
> obj-y += nand/
> obj-y += nor/
> obj-y += usb/
> obj-$(CONFIG_SPI) += spi/
> obj-$(CONFIG_I2C) += i2c/
> obj-$(CONFIG_VIDEO) += video/
>
>
> is there a fundamental reason that some of those subdirs are
> auto-selected, while others are based on a CONFIG variable? asked
> another way, are there some driver subdirs that are so fundamentally
> required that they *should* be auto-selected, or should *everything*
> be a user-selectable choice? the above just seems slightly
> inconsistent and non-obvious.
Nothing of the above is really fundamental. Without serial drivers you
won't see anything of course, but this won't stop barebox from working.
I think this only reflects a change of taste during time and should be
done consistently so that other people know how to do it. Prefered is
the obj-$(CONFIG_SPI) += spi/ style.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2009-12-23 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 15:02 Robert P. J. Day
2009-12-22 15:23 ` Robert Schwebel
2009-12-22 15:30 ` Robert P. J. Day
2009-12-23 9:06 ` Sascha Hauer [this message]
2009-12-23 9:11 ` Robert Schwebel
2009-12-23 9:19 ` Robert P. J. Day
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=20091223090639.GP15126@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/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