public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa.com>
To: Alan Curry <pacman@theworld.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Pegasos keyboard detection
Date: Tue, 07 Aug 2007 17:27:09 +0100	[thread overview]
Message-ID: <46B89D5D.9090506@genesi-usa.com> (raw)
In-Reply-To: <200708070416.l774G3Qf728075@shell01.TheWorld.com>


Okay, you don't need to be an experienced Open Firmware developer.

In fact I know we have had experienced Open Firmware developers who have
said that our firmware sucks (some comment about "shitty German engineering",
I really did quit caring after that point) because they could not run probe-all
from the "ok" prompt.

In the first few pages of the OF spec, it very clearly states that this will
probably make your system explode.

So even experts do not know what they are doing. I don't expect users to.
But as an engineer, here, I think patching the device-type in the boot
wrapper (be it the chrp boot loader) is the wrong place, because we have
had real experts here (Ben, Segher etc.) complain that fixing the device
tree in the boot wrapper is no substitute for a correctly working
firmware.

-- 
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations

Alan Curry wrote:
> I'm almost sorry I spoke up...
> 
> Matt Sealey writes the following:
>> Okay before you add to the nvramrc you also need to add probe-all to build the
>> device tree first; I assumed this was common knowledge.
> 
> Maybe for experienced OpenFirmware developers; this is the first time I've
> had to touch the stuff. So first I had to learn Forth. To patch the kernel
> you only need to know C. (Of course I already knew C -- it's common
> knowledge.)
> 

      reply	other threads:[~2007-08-07 16:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23  6:16 keyboard not found in 2.6.22.1 Alan Curry
2007-07-25  1:28 ` [PATCH] powerpc: Pegasos keyboard detection Alan Curry
2007-07-25  6:22   ` Benjamin Herrenschmidt
2007-07-25  6:45     ` Alan Curry
2007-07-25  7:12   ` Benjamin Herrenschmidt
2007-07-27  1:48     ` Andrew Morton
2007-07-27  3:00       ` Benjamin Herrenschmidt
2007-07-27  4:22         ` Andrew Morton
2007-07-27  4:48           ` Alan Curry
2007-07-27  7:15           ` Benjamin Herrenschmidt
2007-07-31 21:26   ` Segher Boessenkool
2007-08-01  7:25     ` Matt Sealey
2007-08-01  7:28       ` Matt Sealey
2007-08-02  4:40       ` Alan Curry
2007-08-06 18:45         ` Segher Boessenkool
2007-08-06 21:40         ` Matt Sealey
2007-08-06 21:57           ` Segher Boessenkool
2007-08-07 16:21             ` Matt Sealey
2007-08-09 16:30               ` Segher Boessenkool
2007-08-09 16:46                 ` Matt Sealey
2007-08-07  4:16           ` Alan Curry
2007-08-07 16:27             ` Matt Sealey [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=46B89D5D.9090506@genesi-usa.com \
    --to=matt@genesi-usa.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=pacman@theworld.com \
    --cc=segher@kernel.crashing.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