public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Debian m68k <debian-68k@lists.debian.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Linux 3.1-2-m68k config (was: Re: Linux 3.10-2-m68k FPU support)
Date: Mon, 11 Nov 2013 16:16:56 +1100 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1311111600420.13170@nippy.intranet> (raw)
In-Reply-To: <Pine.BSM.4.64L.1311110108550.15024@herc.mirbsd.org>


On Mon, 11 Nov 2013, Thorsten Glaser wrote:

> Finn Thain dixit:
> 
> > ! multi_defconfig -----------------------------+
> > ! config-3.10-2-m68k ------------------------+ |
> > !                                            | |
> > 
> > ...
> > 
> > ! 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 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.

When something goes wrong, and the kernel messages aren't available to 
tell you what went wrong, then you may lack the information you need to 
support those things that you are willing to support.

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.

> ...
> Besides, if multi_defconfig has it as "n"...

That should be OK; all of my test kernel configs also disable these 
options.

Finn

  reply	other threads:[~2013-11-11  5:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-20  8:52 Linux 3.1-2-m68k config (was: Re: Linux 3.10-2-m68k FPU support) Geert Uytterhoeven
2013-10-20  9:25 ` Laurent Vivier
2013-10-20  9:34   ` Geert Uytterhoeven
2013-10-20 15:01   ` Linux 3.1-2-m68k config Thorsten Glaser
2013-10-20 16:49     ` Geert Uytterhoeven
2013-10-21  4:39 ` Linux 3.1-2-m68k config (was: Re: Linux 3.10-2-m68k FPU support) Finn Thain
2013-10-21  9:03   ` Linux 3.1-2-m68k config Thorsten Glaser
2013-11-11  0:13 ` Linux 3.1-2-m68k config (was: Re: Linux 3.10-2-m68k FPU support) Finn Thain
2013-11-11  1:10   ` Thorsten Glaser
2013-11-11  5:16     ` Finn Thain [this message]
2013-11-11  9:33       ` Geert Uytterhoeven
2013-11-11 14:20         ` Thorsten Glaser
2013-11-12  0:21         ` Finn Thain
2013-11-12  8:44           ` Geert Uytterhoeven

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=alpine.LNX.2.00.1311111600420.13170@nippy.intranet \
    --to=fthain@telegraphics.com.au \
    --cc=debian-68k@lists.debian.org \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@vger.kernel.org \
    --cc=tg@mirbsd.de \
    /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