a. why does SONY_ACPI default to m ? Other similar options are default n.
b. config LSF
bool "Support for Large Single Files"
depends on X86 || (MIPS && 32BIT) || PPC32 || ARCH_S390_31 || SUPERH || UML
default n
help
When CONFIG_LBD is disabled, say Y here if you want to
handle large file(bigger than 2TB), otherwise say N.
When CONFIG_LBD is enabled, Y is set automatically.
This config option appears to be unimplemented and the Help text is
incorrect: it is not set to Y automatically when CONFIG_LBD is enabled.
Where did this come from?
---
~Randy
"Randy.Dunlap" <[email protected]> wrote:
>
>
> a. why does SONY_ACPI default to m ? Other similar options are default n.
Because I got heartily sick of losing the setting each time I went back to
a mainline kernel and did `make oldconfig'.
> b. config LSF
> bool "Support for Large Single Files"
> depends on X86 || (MIPS && 32BIT) || PPC32 || ARCH_S390_31 || SUPERH || UML
> default n
> help
> When CONFIG_LBD is disabled, say Y here if you want to
> handle large file(bigger than 2TB), otherwise say N.
> When CONFIG_LBD is enabled, Y is set automatically.
>
> This config option appears to be unimplemented and the Help text is
> incorrect: it is not set to Y automatically when CONFIG_LBD is enabled.
> Where did this come from?
2tb-files-*.patch.
That config option needs to go away, but the developer didn't seem to agree
with or appreciate that at the time.
>> a. why does SONY_ACPI default to m ? Other similar options
>are default n.
>
>Because I got heartily sick of losing the setting each time I
>went back to a mainline kernel and did `make oldconfig'.
IIR the recommendation from Roman on these things was
to remove the default entirely. If you have a favorite
.config file with =m in it, then make oldconfig should
preserve that choice.
-Len
"Brown, Len" <[email protected]> wrote:
>
>
> >> a. why does SONY_ACPI default to m ? Other similar options
> >are default n.
> >
> >Because I got heartily sick of losing the setting each time I
> >went back to a mainline kernel and did `make oldconfig'.
>
> IIR the recommendation from Roman on these things was
> to remove the default entirely. If you have a favorite
> .config file with =m in it, then make oldconfig should
> preserve that choice.
>
Nope. Once you remove the Kconfig entry entirely (ie: go back to a
mainline kernel), `make oldconfig' will rub that config entry out
completely.
On Sun, 26 Feb 2006 19:51:09 -0800 Andrew Morton wrote:
> "Brown, Len" <[email protected]> wrote:
> >
> >
> > >> a. why does SONY_ACPI default to m ? Other similar options
> > >are default n.
> > >
> > >Because I got heartily sick of losing the setting each time I
> > >went back to a mainline kernel and did `make oldconfig'.
> >
> > IIR the recommendation from Roman on these things was
> > to remove the default entirely. If you have a favorite
> > .config file with =m in it, then make oldconfig should
> > preserve that choice.
> >
>
> Nope. Once you remove the Kconfig entry entirely (ie: go back to a
> mainline kernel), `make oldconfig' will rub that config entry out
> completely.
Yes. So you have it =m so that it will build in your
test builds, right? or some other reason?
thanks,
---
~Randy
"Randy.Dunlap" <[email protected]> wrote:
>
> On Sun, 26 Feb 2006 19:51:09 -0800 Andrew Morton wrote:
>
> > "Brown, Len" <[email protected]> wrote:
> > >
> > >
> > > >> a. why does SONY_ACPI default to m ? Other similar options
> > > >are default n.
> > > >
> > > >Because I got heartily sick of losing the setting each time I
> > > >went back to a mainline kernel and did `make oldconfig'.
> > >
> > > IIR the recommendation from Roman on these things was
> > > to remove the default entirely. If you have a favorite
> > > .config file with =m in it, then make oldconfig should
> > > preserve that choice.
> > >
> >
> > Nope. Once you remove the Kconfig entry entirely (ie: go back to a
> > mainline kernel), `make oldconfig' will rub that config entry out
> > completely.
>
> Yes. So you have it =m so that it will build in your
> test builds, right? or some other reason?
>
As I said, I got tired of losing the setting and not being able to control
the backlight brightness. <insert anecdote about sitting outside at son's
basketball game, having to recompile entire kernel by smell so I could read
the screen>
>> >> a. why does SONY_ACPI default to m ? Other similar options
>> >are default n.
>> >
>> >Because I got heartily sick of losing the setting each time I
>> >went back to a mainline kernel and did `make oldconfig'.
>>
>> IIR the recommendation from Roman on these things was
>> to remove the default entirely. If you have a favorite
>> .config file with =m in it, then make oldconfig should
>> preserve that choice.
>>
>
>Nope. Once you remove the Kconfig entry entirely (ie: go back to a
>mainline kernel), `make oldconfig' will rub that config entry out
>completely.
You're deleting the .config entirely and running "make oldconfig"
from scratch?
Hmmm, I always keep my sane .config around and run "make oldconfig"
on top of it in the context of the new kernel. That preserves
my non-default selections.
-Len