From: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
To: Larry Finger <larry.finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
John Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Subject: Re: [PATCH] bcm43xx: Fix failure to deliver PCI-E interrupts
Date: Fri, 12 Jan 2007 17:53:05 +0100 [thread overview]
Message-ID: <200701121753.06014.mb@bu3sch.de> (raw)
In-Reply-To: <45A7B914.4030804-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
On Friday 12 January 2007 17:36, Larry Finger wrote:
> Michael Buesch wrote:
>
> I have one general question before I address your comments. Does a BCM43xx chip always have either a
> PCI or a PCI-E core? I've seen discussion on this list that makes me wonder. That is why I had some
> explicit tests for PCI-E in the code.
Ok, I see your point.
I don't think we have devices without PCI core.
BUT:
If you think there are devices without a PCI core, you
must not switch to it in the first place. So your check is
worthless nevertheless, because in case of no PCI core you
have crashed much earlier anyway. ;)
If we have a PCI core (and I think we always have), it can only
be PCI or PCIE.
--
Greetings Michael.
prev parent reply other threads:[~2007-01-12 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 4:52 [PATCH] bcm43xx: Fix failure to deliver PCI-E interrupts Larry Finger
[not found] ` <45a713f4.CVklfeegOYfmrIW+%Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2007-01-12 14:17 ` Michael Buesch
2007-01-12 16:36 ` Larry Finger
[not found] ` <45A7B914.4030804-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2007-01-12 16:53 ` Michael Buesch [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=200701121753.06014.mb@bu3sch.de \
--to=mb-fseuscv1ubazqb+pc5nmwq@public.gmane.org \
--cc=bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=larry.finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).