Hi!
> > > > Configuring kernels from scratch has become an incredibly long and
> > > > tedious task. The reason is that the number of drivers and options has
> > > > exploded in the past few years. Which in itself is great - Linux is
> > > > successful, yeah! - but the side effects must be dealt
Hi!
Configuring kernels from scratch has become an incredibly long and
tedious task. The reason is that the number of drivers and options has
exploded in the past few years. Which in itself is great - Linux is
successful, yeah! - but the side effects must be dealt with.
Hi!
> Ideally, the arch doesn't matter at all for a driver, only the
> infrastructure the driver depends on does. So perhaps the
Actually, it would be nice if user was never asked for combination
that can be compiled, and kernel would support them, but there's no
such hardware.
For example, if
Hi!
Ideally, the arch doesn't matter at all for a driver, only the
infrastructure the driver depends on does. So perhaps the
Actually, it would be nice if user was never asked for combination
that can be compiled, and kernel would support them, but there's no
such hardware.
For example, if I
On Mon, 14 Apr 2014 21:52:14 -0700, Greg KH wrote:
> I'd argue that your build systems need to get faster, the laptop I'm
> typing this on can do a full modconfig build, with over 3000 modules, in
> around 20 minutes. My build server in the cloud can do that in less
> than 5 minutes, and that's
On Mon, 14 Apr 2014 21:52:14 -0700, Greg KH wrote:
I'd argue that your build systems need to get faster, the laptop I'm
typing this on can do a full modconfig build, with over 3000 modules, in
around 20 minutes. My build server in the cloud can do that in less
than 5 minutes, and that's not a
On 04/15/2014 03:54 AM, Jean Delvare wrote:
> Hi Greg,
>
> On Mon, 14 Apr 2014 21:52:14 -0700, Greg KH wrote:
>> On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
>
>> I do 'allmodconfig'
>> builds all the time, with over 3000 modules. The build works just fine
>> on "modern"
On Tue, Apr 15, 2014 at 11:24 AM, Greg KH wrote:
> On Tue, Apr 15, 2014 at 07:50:05AM -0400, Josh Boyer wrote:
>> On Tue, Apr 15, 2014 at 12:52 AM, Greg KH wrote:
>> > On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
>> >> And it's not going to get any better over time. As others
On Tue, Apr 15, 2014 at 07:50:05AM -0400, Josh Boyer wrote:
> On Tue, Apr 15, 2014 at 12:52 AM, Greg KH wrote:
> > On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
> >> And it's not going to get any better over time. As others have already
> >> mentioned, most new drivers these days
On Tue, Apr 15, 2014 at 12:52 AM, Greg KH wrote:
> On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
>> And it's not going to get any better over time. As others have already
>> mentioned, most new drivers these days are NOT for x86, they are for
>> ARM, AVR32 and other fancy embedded
Hi Greg,
On Mon, 14 Apr 2014 21:52:14 -0700, Greg KH wrote:
> On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
> > In the case above, yes. But I don't quite see how that makes a
> > difference. x86 has platform drivers too, they are the essence of the
> > mfd framework. Almost every
On 2014-04-15 06:52, Greg KH wrote:
> On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
>> I'm very fine with USB drivers being architecture-agnostic. They really
>> are. But in practice a lot of PCI and platform drivers are only useful
>> of one architecture, of a few ones at best.
>
Hi Greg,
On Mon, 14 Apr 2014 21:53:34 -0700, Greg KH wrote:
> On Mon, Apr 14, 2014 at 03:59:11PM -0400, Josh Boyer wrote:
> >
> > Maybe I'm overly grumpy. Still, it's frustrating to see Kconfig
> > entries that clearly say "blahblah found on foo ARM chip" in the help
> > with no "depends on
Hi Greg,
On Mon, 14 Apr 2014 21:53:34 -0700, Greg KH wrote:
On Mon, Apr 14, 2014 at 03:59:11PM -0400, Josh Boyer wrote:
Maybe I'm overly grumpy. Still, it's frustrating to see Kconfig
entries that clearly say blahblah found on foo ARM chip in the help
with no depends on ARM (not
On 2014-04-15 06:52, Greg KH wrote:
On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
I'm very fine with USB drivers being architecture-agnostic. They really
are. But in practice a lot of PCI and platform drivers are only useful
of one architecture, of a few ones at best.
Why
Hi Greg,
On Mon, 14 Apr 2014 21:52:14 -0700, Greg KH wrote:
On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
In the case above, yes. But I don't quite see how that makes a
difference. x86 has platform drivers too, they are the essence of the
mfd framework. Almost every
On Tue, Apr 15, 2014 at 12:52 AM, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
And it's not going to get any better over time. As others have already
mentioned, most new drivers these days are NOT for x86, they are for
ARM, AVR32 and
On Tue, Apr 15, 2014 at 07:50:05AM -0400, Josh Boyer wrote:
On Tue, Apr 15, 2014 at 12:52 AM, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
And it's not going to get any better over time. As others have already
mentioned, most new
On Tue, Apr 15, 2014 at 11:24 AM, Greg KH gre...@linuxfoundation.org wrote:
On Tue, Apr 15, 2014 at 07:50:05AM -0400, Josh Boyer wrote:
On Tue, Apr 15, 2014 at 12:52 AM, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
And it's not going
On 04/15/2014 03:54 AM, Jean Delvare wrote:
Hi Greg,
On Mon, 14 Apr 2014 21:52:14 -0700, Greg KH wrote:
On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
I do 'allmodconfig'
builds all the time, with over 3000 modules. The build works just fine
on modern hardware.
I'd
On Mon, Apr 14, 2014 at 03:59:11PM -0400, Josh Boyer wrote:
>
> Maybe I'm overly grumpy. Still, it's frustrating to see Kconfig
> entries that clearly say "blahblah found on foo ARM chip" in the help
> with no "depends on ARM" (not meaning to pick on ARM). I would like
> to think there is some
On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
> Hi Greg,
>
> On Mon, 14 Apr 2014 12:11:43 -0700, Greg KH wrote:
> > On Mon, Apr 14, 2014 at 02:53:59PM +0200, Jean Delvare wrote:
> > > Configuring kernels from scratch has become an incredibly long and
> > > tedious task. The reason
Hi Greg,
On Mon, 14 Apr 2014 12:11:43 -0700, Greg KH wrote:
> On Mon, Apr 14, 2014 at 02:53:59PM +0200, Jean Delvare wrote:
> > Configuring kernels from scratch has become an incredibly long and
> > tedious task. The reason is that the number of drivers and options has
> > exploded in the past
On Mon, Apr 14, 2014 at 3:11 PM, Greg KH wrote:
> On Mon, Apr 14, 2014 at 02:53:59PM +0200, Jean Delvare wrote:
>> Hi all,
>>
>> Configuring kernels from scratch has become an incredibly long and
>> tedious task. The reason is that the number of drivers and options has
>> exploded in the past few
On Mon, Apr 14, 2014 at 02:53:59PM +0200, Jean Delvare wrote:
> Hi all,
>
> Configuring kernels from scratch has become an incredibly long and
> tedious task. The reason is that the number of drivers and options has
> exploded in the past few years. Which in itself is great - Linux is
>
On Mon, Apr 14, 2014 at 8:53 AM, Jean Delvare wrote:
> Hi all,
>
> Configuring kernels from scratch has become an incredibly long and
> tedious task. The reason is that the number of drivers and options has
> exploded in the past few years. Which in itself is great - Linux is
> successful, yeah!
Hi all,
Configuring kernels from scratch has become an incredibly long and
tedious task. The reason is that the number of drivers and options has
exploded in the past few years. Which in itself is great - Linux is
successful, yeah! - but the side effects must be dealt with.
6000-line .config
On Mon, Apr 14, 2014 at 11:12:54PM +0200, Jean Delvare wrote:
Hi Greg,
On Mon, 14 Apr 2014 12:11:43 -0700, Greg KH wrote:
On Mon, Apr 14, 2014 at 02:53:59PM +0200, Jean Delvare wrote:
Configuring kernels from scratch has become an incredibly long and
tedious task. The reason is that
On Mon, Apr 14, 2014 at 03:59:11PM -0400, Josh Boyer wrote:
Maybe I'm overly grumpy. Still, it's frustrating to see Kconfig
entries that clearly say blahblah found on foo ARM chip in the help
with no depends on ARM (not meaning to pick on ARM). I would like
to think there is some balance
Hi all,
Configuring kernels from scratch has become an incredibly long and
tedious task. The reason is that the number of drivers and options has
exploded in the past few years. Which in itself is great - Linux is
successful, yeah! - but the side effects must be dealt with.
6000-line .config
On Mon, Apr 14, 2014 at 8:53 AM, Jean Delvare jdelv...@suse.de wrote:
Hi all,
Configuring kernels from scratch has become an incredibly long and
tedious task. The reason is that the number of drivers and options has
exploded in the past few years. Which in itself is great - Linux is
On Mon, Apr 14, 2014 at 02:53:59PM +0200, Jean Delvare wrote:
Hi all,
Configuring kernels from scratch has become an incredibly long and
tedious task. The reason is that the number of drivers and options has
exploded in the past few years. Which in itself is great - Linux is
successful,
On Mon, Apr 14, 2014 at 3:11 PM, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Apr 14, 2014 at 02:53:59PM +0200, Jean Delvare wrote:
Hi all,
Configuring kernels from scratch has become an incredibly long and
tedious task. The reason is that the number of drivers and options has
exploded
Hi Greg,
On Mon, 14 Apr 2014 12:11:43 -0700, Greg KH wrote:
On Mon, Apr 14, 2014 at 02:53:59PM +0200, Jean Delvare wrote:
Configuring kernels from scratch has become an incredibly long and
tedious task. The reason is that the number of drivers and options has
exploded in the past few
34 matches
Mail list logo
