From: Matt Porter <mporter@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: David Gardiner <daveg@sonartech.com.au>, linuxppc-embedded@ozlabs.org
Subject: Re: powerpc with gigabit card hanging
Date: Tue, 28 Sep 2004 00:01:24 -0700 [thread overview]
Message-ID: <20040928000124.H30772@home.com> (raw)
In-Reply-To: <FB412DE8-1119-11D9-8370-000A95A4DC02@kernel.crashing.org>; from segher@kernel.crashing.org on Tue, Sep 28, 2004 at 01:45:27AM -0500
On Tue, Sep 28, 2004 at 01:45:27AM -0500, Segher Boessenkool wrote:
> >> Sure. But the interrupt _assignment_ should be done by firmware.
> >
> > I can't argue with ideaology.
>
> It's not ideology; it's what the PCI spec says.
>
> >> p.s. And I know this isn't always practically possible; but why
> >> then support a product like that at all, in the Open Source
> >> community?
> >
> > By this reasoning, we should also not support the many BIOS/OF
> > platforms that report incorrect data and have to have their
> > reported data fixed up by the kernel. That's gross too by the
> > same measure.
>
> There is a difference between patching some errors and doing
> all the work yourself.
I see your point of view and disagree.
> But hey, let not me stop you from doing this.
Don't worry, you won't. :)
-Matt
next prev parent reply other threads:[~2004-09-28 7:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 4:32 powerpc with gigabit card hanging David Gardiner
2004-09-24 15:01 ` Segher Boessenkool
2004-09-28 3:41 ` David Gardiner
2004-09-28 5:13 ` Matt Porter
[not found] ` <C617C694-1110-11D9-8370-000A95A4DC02@kernel.crashing.org>
2004-09-28 5:48 ` Matt Porter
2004-09-28 5:58 ` Segher Boessenkool
2004-09-28 6:14 ` Matt Porter
2004-09-28 6:23 ` Segher Boessenkool
2004-09-28 6:37 ` Matt Porter
2004-09-28 6:45 ` Segher Boessenkool
2004-09-28 7:01 ` Matt Porter [this message]
2004-09-28 7:10 ` Segher Boessenkool
2004-09-28 6:46 ` David Gardiner
2004-09-28 6:59 ` Matt Porter
2004-09-28 22:45 ` David Gardiner
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=20040928000124.H30772@home.com \
--to=mporter@kernel.crashing.org \
--cc=daveg@sonartech.com.au \
--cc=linuxppc-embedded@ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).