On Tue, Nov 12, 2013 at 1:21 AM, Finn Thain wrote:
>> > Hence I was trying to find an explanation for the screen shot posted,
>> > which says "console [tty0] enabled" even though the macfb console did
>> > not appear.
>>
>> No, without fb/console support you wouldn't even see those.
>
> "console [
On Mon, 11 Nov 2013, Geert Uytterhoeven wrote:
> On Mon, Nov 11, 2013 at 6:16 AM, Finn Thain
> wrote:
> >> > ! CONFIG_FB_SYS_COPYAREA : m n
> >> > ! CONFIG_FB_SYS_FILLRECT : m n
> >> > ! CONFIG_FB_SYS_FOPS : m n
> >> > ! CONFIG_FB_SYS_IM
Geert Uytterhoeven dixit:
>On Mon, Nov 11, 2013 at 6:16 AM, Finn Thain wrote:
>>> > ! CONFIG_FB_SYS_COPYAREA : m n
>>> > ! CONFIG_FB_SYS_FILLRECT : m n
>>> > ! CONFIG_FB_SYS_FOPS : m n
>>> > ! CONFIG_FB_SYS_IMAGEBLIT : m n
On Mon, Nov 11, 2013 at 6:16 AM, Finn Thain wrote:
>> > ! CONFIG_FB_SYS_COPYAREA : m n
>> > ! CONFIG_FB_SYS_FILLRECT : m n
>> > ! CONFIG_FB_SYS_FOPS : m n
>> > ! CONFIG_FB_SYS_IMAGEBLIT : m n
>> >
>> >Would this prevent the
On Mon, 11 Nov 2013, Thorsten Glaser wrote:
> Finn Thain dixit:
>
> > ! multi_defconfig -+
> > ! config-3.10-2-m68k + |
> > !| |
> >
> > ...
> >
> > ! CONFIG_FB_SYS_COPYAREA : m n
Finn Thain dixit:
>Would this prevent the macfb framebuffer console from working in the
>absence of kernel modules?
With the switch to initrd, absence of modules is simply no longer
supported at all, period. I am not happy about this myself, but,
realistically, the monoliths cannot be kept worki
On Sun, 20 Oct 2013, Geert Uytterhoeven wrote:
> This is the difference between my multi_defconfig and config-3.10-2-m68k.
...
>
> ! multi_defconfig -+
> ! config-3.10-2-m68k + |
> !| |
...
> ! CO
Finn Thain dixit:
>CONFIG_ADB_MACIISI is disabled in -multi due to crashing bugs. Debian
>might want to do the same (until I get a chance to fix it). The serial
OK, thanks.
>Below is the same list after sort -k4 -k5 -k2. Note that some modules in
>-multi are disabled in the Debian config. Tha
On Sun, 20 Oct 2013, Geert Uytterhoeven wrote:
> This is the difference between my multi_defconfig and
> config-3.10-2-m68k.
Nice!
> Big differences are due to many drivers being modular in the initrd for
> the Debian kernel, which I want to avoid for my defconfigs, for
> hassle-free testing
On Sun, Oct 20, 2013 at 5:01 PM, Thorsten Glaser wrote:
> One pet peeve of mine is that I don’t know which of the tristate
> options add “common code” (such as hooks) and which, when set to
> ‘m’, do _not_ add something to vmlinux.
To find code that's compiled if a tristate symbol is "m":
git gr
Geert Uytterhoeven dixit:
>Big differences are due to many drivers being modular in the initrd for the
>Debian kernel, which I want to avoid for my defconfigs, for hassle-free
>testing.
ACK, but we need that.
>What sticks out:
> - Lack of FPU emulation support in the Debian kernel,
Hm okay.
>
On Sun, Oct 20, 2013 at 11:25 AM, Laurent Vivier wrote:
> Le 20/10/2013 10:52, Geert Uytterhoeven a écrit :
>>
>> On Sat, Oct 19, 2013 at 6:13 PM, Geert Uytterhoeven
>> wrote:
>> [...]
>>
>>
>> Apart from that, (probably both) configs need more stripping in the common
>> part. I want to have boot
Le 20/10/2013 10:52, Geert Uytterhoeven a écrit :
On Sat, Oct 19, 2013 at 6:13 PM, Geert Uytterhoeven
wrote:
[...]
Apart from that, (probably both) configs need more stripping in the common
part. I want to have bootable (i.e. < 4 MiB) defconfig kernels.
Moreover, a compressed kernel fitting on
On Sat, Oct 19, 2013 at 6:13 PM, Geert Uytterhoeven
wrote:
> Doh, I really should have an in-depth look at your .config, and compare it to
> multi_defconfig (which does need more stripping!), to catch these things.
This is the difference between my multi_defconfig and config-3.10-2-m68k.
Big diff
14 matches
Mail list logo
