Hi Behan,
On Tue, 29 Jul 2008, Behan Webster wrote:
> However, most notably it contains a utility called "elbs-rootfs" which
> makes it easy to create an embedded rootfs for any architecture
> supported by the Debian projecy (or Ubuntu Linux). The idea is to get a
> rootfs up and working
Le Mon, 4 Aug 2008 14:16:41 -0400,
"J. Bruce Fields" <[EMAIL PROTECTED]> a écrit :
> OK by me, but again, why exactly? Since you're replacing the locking
> calls they used by stubs that just return errors, in theory nfs, nfsd,
> gfs2, and the rest should still compile and run, just without lockin
On Aug 6, 2008, at 12:44 PM, René Rebe wrote:
Heh, you might also consider using "off the shelf" build systems, such
as the T2 SDE:
http://t2-project.org
To avoid re-inventing the wheel again and again.
Yours,
Whee.. another rootfs build system. Why we can't converge some of
these tow
Add support for a built-in command line for x86 architectures.
The Kconfig help gives the major rationale for this addition.
Note that this option is available for many other arches, and
its use is widespread in embedded projects.
This patch addresses concerns that were raised with an
earlier ver
On Wed, Aug 06, 2008 at 02:31:48PM -0700, Tim Bird wrote:
> Add support for a built-in command line for x86 architectures.
> The Kconfig help gives the major rationale for this addition.
If this feature is desired on all architectures, shouldn't it go out of
arch/?
rsc
--
Dipl.-Ing. Robert Schw
On Wed, 2008-08-06 at 14:31 -0700, Tim Bird wrote:
> The default behavior is to append the boot loader string
> to this one. However, there is a mechanism (leading '!')
> to force the built-in string to override the boot loader
> string.
Nice solution.
Where is this relative to early boot optio
Robert Schwebel wrote:
> On Wed, Aug 06, 2008 at 02:31:48PM -0700, Tim Bird wrote:
>> Add support for a built-in command line for x86 architectures.
>> The Kconfig help gives the major rationale for this addition.
>
> If this feature is desired on all architectures, shouldn't it go out of
> arch/?
Matt Mackall wrote:
> On Wed, 2008-08-06 at 14:31 -0700, Tim Bird wrote:
>> The default behavior is to append the boot loader string
>> to this one. However, there is a mechanism (leading '!')
>> to force the built-in string to override the boot loader
>> string.
>
> Nice solution.
>
> Where is
Tim Bird wrote:
One difficulty is that the other arches' command lines
are not currently "broken", so there's no real incentive
to change them.
The only thing novel thing I'm adding here is the addition of
the leading '!' to allow for an override. This is needed
in some x86 cases I'm familiar
On Wed, 2008-08-06 at 15:31 -0700, Tim Bird wrote:
> Matt Mackall wrote:
> > On Wed, 2008-08-06 at 14:31 -0700, Tim Bird wrote:
> >> The default behavior is to append the boot loader string
> >> to this one. However, there is a mechanism (leading '!')
> >> to force the built-in string to override
On Wed, 2008-08-06 at 15:48 -0700, H. Peter Anvin wrote:
> Tim Bird wrote:
> >
> > One difficulty is that the other arches' command lines
> > are not currently "broken", so there's no real incentive
> > to change them.
> >
> > The only thing novel thing I'm adding here is the addition of
> > the
H. Peter Anvin wrote:
> Tim Bird wrote:
>> The only thing novel thing I'm adding here is the addition of
>> the leading '!' to allow for an override. This is needed
>> in some x86 cases I'm familiar with, but I've haven't seen
>> any cases where it would be useful for other arches.
>> (not to say
Matt Mackall wrote:
On Wed, 2008-08-06 at 15:48 -0700, H. Peter Anvin wrote:
Tim Bird wrote:
One difficulty is that the other arches' command lines
are not currently "broken", so there's no real incentive
to change them.
The only thing novel thing I'm adding here is the addition of
the leading
Tim Bird wrote:
CONFIG_CMDLINE_OVERRIDE is probably more palatable to other architectures.
I'd be OK implementing it with an option, rather than a magic char.
I was trying to avoid adding too many options, since many kernel
developers prefer fewer options where possible. But the magic
char m
Hi,
It seems that there is a small problem when kernel parses the command
line passed by u-boot.
For example, when I add "board=myboard boardid=1" in the command line
and register handler in kernel as __setup("board", board_setup), then
the board_setup function is called twice : once with argumen
15 matches
Mail list logo
