From: David W Studeman <avionicsdv@aim.com>
To: linux-kernel@vger.kernel.org
Subject: Keyboard Jammed error patch 2.4.35-pre4
Date: Sun, 27 Jul 2008 23:59:47 -0700 [thread overview]
Message-ID: <g6jqud$t5e$1@ger.gmane.org> (raw)
Hello! The changes that were made on 04-25-2007 as "[PATCH
2.4.35-pre4] fix 'pc_keyb: controller jammed (0xA7)' error" have broken
the ability to compile with no keyboard and no VT support. This mainly
affects Cobalt machines which do not have dmi present as these use a
flashrom to boot with and not a typical bios so dmi blacklisting would
be pointless unless it allowed for no dmi present and then blacklist. I
had to create a patch against 2.4.34 to restore the ability to compile
with no keyboard and VT support.
With keyboard support whether embedded or modularized, in a Raq/Qube3
and Raq4, it simply gives off a warning in the serial console if you are
watching it boot, a Raq 550 on the other hand shows it as an error about
300 times and will also show up in the dmesg log. Unless one was to fix
the dmi blacklisting to disable when no dmi is present as is the case
here, it needs to be fixed to allow compiling without. A Cobalt can only
use two methods of terminal access, one being serial console and ssh
being the other.
These units do not use a typical bios but rather a flashrom on a 1 OR
2mb flash chip depending on model. The flashrom image contains it's own
kernel and Cobalt utilities and starts it's own boot process and looks
for a bzipped vmlinux image in boot to hand off to when it's time to
actually boot your OS. You have to set the boot and root partition in it
the first time and it does not care about or see any bootloader you may
have installed. It also does not give off any info about itself either.
Sure, the required embedded Cobalt drivers will tell something from
/proc/cobalt but that's about it.
This ability to compile without had been broken and restored back in
kernel 2.4.31 and then as of the 2.4.35.4 it has been broken since. I'm
involved in making a Cobalt build of IPCop and would love it if I didn't
have to patch for this in addition to the rest that is required to make
a Raq/Qube run.
Dave Studeman
next reply other threads:[~2008-07-28 7:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 6:59 David W Studeman [this message]
2008-07-29 5:15 ` Keyboard Jammed error patch 2.4.35-pre4 Willy Tarreau
2008-07-30 7:22 ` David W Studeman
2008-07-30 7:51 ` Willy Tarreau
2008-07-30 10:39 ` David W Studeman
2008-07-30 12:38 ` Willy Tarreau
2008-09-21 13:00 ` David W Studeman
2008-09-21 14:40 ` Willy Tarreau
2008-09-22 3:30 ` David W Studeman
2008-09-22 4:18 ` Willy Tarreau
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='g6jqud$t5e$1@ger.gmane.org' \
--to=avionicsdv@aim.com \
--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