Geert Uytterhoeven dixit:
>On Mon, Nov 11, 2013 at 6:16 AM, Finn Thain <fth...@telegraphics.com.au> 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 macfb framebuffer console from working in the
>>> >absence of kernel modules?
>> 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
I see.
>> 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.
OK.
>Indeed. Mac needs the CONFIG_FB_CFB_* counterparts.
>
>CONFIG_FB_SYS_* is for system RAM, while CONFIG_FB_CFB_*
>is for iomem. Not that it would matter much on m68k, m68k has no
>strict separation between both.
OK. So there needs to be no further change then those already
submitted to the Debian Linux maintainers in #728392 correct?
bye,
//mirabilos
--
„Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund,
mksh auf jedem System zu installieren.“
-- XTaran auf der OpenRheinRuhr, ganz begeistert
(EN: “[…]uhr.gz is a reason to install mksh on every system.”)
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/pine.bsm.4.64l.1311111418320.23...@herc.mirbsd.org
