linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org, Alan Curry <pacman@TheWorld.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Pegasos keyboard detection
Date: Thu, 9 Aug 2007 18:30:35 +0200	[thread overview]
Message-ID: <909c5e405e5cd26bca3aff13fe55adbc@kernel.crashing.org> (raw)
In-Reply-To: <46B89C10.7090507@genesi-usa.com>

>> That's hardly the only reason.  But yeah, that's one way to
>> implement the workaround, but _we_ (the Linux community) cannot
>> do it like that (easily) for all users.
>
> But you're the guy who told us our firmware sucks and we should fix our
> firmware

Yes, and?  You _should_ fix your firmware, it is buggy after all.
Esp. back then as it wasn't shipping yet.

> rather than clutter Linux with too many fixups.

Also, putting fixups in the wrapper is a wholly different thing from
putting fixups deep inside the kernel code proper.

> Linux is already a bad enough moving target, and none of these fixes 
> help
> other operating systems or developers, if we only patch Linux,

But that's not Linux' concern.  You might care, we don't.  Is
this so hard to understand?

> 1) the reports as we had when Efika was released and continually levied
> against Pegasos firmware, that the firmware is broken and must be fixed
> to comply, and no fixes will be considered because "bplan sucks and 
> must
> fix it"
>
> 2) As long as the patches are 2 lines big, you will allow them in, 
> because
> it is too much for a user to update firmware or run a script to boot?

Our only two concerns are what is best on technical grounds, and what
is best for our users.

> Would you guys rather we shipped a boot script that ran the OS, fixed
> all these issues in-place in-firmware, so Linux did not have to have 
> these
> workarounds,

Sure, if you can do that, that would be great.


Segher

  reply	other threads:[~2007-08-09 16:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200707230616.l6N6GaPg1212004@shell01.TheWorld.com>
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 [this message]
2007-08-09 16:46                 ` Matt Sealey
2007-08-07  4:16           ` Alan Curry
2007-08-07 16:27             ` Matt Sealey

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=909c5e405e5cd26bca3aff13fe55adbc@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matt@genesi-usa.com \
    --cc=pacman@TheWorld.com \
    /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;
as well as URLs for NNTP newsgroup(s).