From: Thomas Kunze <thommycheck@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: kernel.bbclass and collie changes
Date: Sat, 26 Jul 2008 11:48:29 +0200 [thread overview]
Message-ID: <488AF2ED.2030709@gmx.de> (raw)
In-Reply-To: <1217065082.22069.111.camel@mill.internal.reciva.com>
Phil Blundell wrote:
> On Fri, 2008-07-25 at 01:56 +0200, Thomas Kunze wrote:
>
>> +/dev/mmcblk0p1 b 6600 0 6 179 1 - - -
>>
>
> Is that "6600" really correct?
>
Of course not. Just a typo.
> It does also seem bit odd having an mmc device in the "minimal" device
> table. I can understand why you need it on collie but I am not sure it
> is all that desirable for device-table-minimal.txt to become the union
> of the devices that everybody needs on their favourite platform for
> booting purposes. Since this is truly a machine specific thing I would
> be inclined to use a separate file, or a collie-specific catenation onto
> the installed copy.
>
I see your point. But OTOH we have 20 hda*, 9 serial consoles and 16 mtd
nodes in there. So its hardly minimal. In my opinion it doesn't hurt to add
a further node.
next prev parent reply other threads:[~2008-07-26 9:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 23:56 RFC: kernel.bbclass and collie changes Thomas Kunze
2008-07-25 3:02 ` Tom Rini
2008-07-25 7:44 ` Andrea Adami
2008-07-25 7:56 ` Marcin Juszkiewicz
2008-07-25 8:09 ` Andrea Adami
2008-07-25 15:55 ` Tom Rini
2008-07-25 16:05 ` Thomas Kunze
2008-07-26 9:38 ` Phil Blundell
2008-07-26 9:48 ` Thomas Kunze [this message]
2008-07-26 10:40 ` Richard Purdie
2008-07-26 11:06 ` Thomas Kunze
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=488AF2ED.2030709@gmx.de \
--to=thommycheck@gmx.de \
--cc=openembedded-devel@lists.openembedded.org \
/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