From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: linux-kernel@vger.kernel.org,
Linux ARM Kernel list <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: [2.6.11.7 / CLPS711x/SkyMinder] module integration issue: keyboard driver _still_ not working after port from 2.4.27
Date: Thu, 21 Apr 2005 19:53:25 +0100 [thread overview]
Message-ID: <20050421185325.GB16160@lkcl.net> (raw)
In-Reply-To: <20050421182845.GA16160@lkcl.net>
okay - i found this:
http://seclists.org/lists/linux-kernel/2000/Mar/0093.html
it talks about "we must force people to choose between vgacon and
fbcon".
when that forcing decision was taken, was dual fbcon-and-serial-console
usage taken into account?
booting with ..... console=ttyCL1 fbcon=vc:1 and then later
on doing modprobe fbcon has exactly the same consequences:
fbcon_takeover is called, the fbcon=vc:1 parameters appear to
be ignored.... greeeeaat.
how the _heck_ am i gonna over-ride the fb_console "setup"
paramaters on a module load, to stop this happening???
i know - HACK TIME!!!
muhahahahah.
l.
On Thu, Apr 21, 2005 at 07:28:45PM +0100, Luke Kenneth Casson Leighton wrote:
> in order to be able to debug what is going on, i have enabled
> a dummy/virtual serial console, all is well so far.
>
> in order to test the screen, i have written, enabled, tested,
> confirmed as reasonably working, a framebuffer driver (which
> i would like to make the console framebuffer - eventually -
> when the serial console is disabled and no longer needed -
> so i am enabling Framebuffer Console support AS WELL as serial
> console support)
>
> now i load the keyboard event module... splat - absolutely no response:
> complete lock-up.
prev parent reply other threads:[~2005-04-21 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 18:28 Luke Kenneth Casson Leighton
2005-04-21 18:53 ` Luke Kenneth Casson Leighton [this message]
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=20050421185325.GB16160@lkcl.net \
--to=lkcl@lkcl.net \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®