netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
To: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
Cc: bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
	John Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V2] bcm43xx: Fix failure to deliver PCI-E interrupts
Date: Fri, 12 Jan 2007 13:27:33 -0600	[thread overview]
Message-ID: <45A7E125.8030009@lwfinger.net> (raw)
In-Reply-To: <200701122001.45546.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>

Michael Buesch wrote:
> On Friday 12 January 2007 19:50, Stephen Sinclair wrote:
>>> The PCI-E modifications to bcm43xx do not set up the interrupt vector
>>> correctly. Tested with BCM4311 (PCI-E) on x86_64 and BCM4306 (PCI) on i386.
>> This was successful for me.  My 4311 is now getting interrupts, and I
>> was able to successfully associate with an AP.  (i386)
> 
> That does the (i386) mean here?
> Were you able to accociate with your PCI or PCI-E card?

Stephen has an i386 system with a PCI-E 4311. The PCI card on i386 was mine, which I tested to make
sure the logic change didn't break the old systems. The display on my old laptop died and wasn't
worth fixing; however, I ssh into it to test on a PCI system.

Larry

  parent reply	other threads:[~2007-01-12 19:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 18:08 [PATCH V2] bcm43xx: Fix failure to deliver PCI-E interrupts Larry Finger
     [not found] ` <45a7ceb2.m02aaCgouBsadVk/%Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2007-01-12 18:50   ` Stephen Sinclair
     [not found]     ` <9b3e2dc20701121050p52e13d92r1ec78e1881bbed3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-01-12 19:01       ` Michael Buesch
     [not found]         ` <200701122001.45546.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2007-01-12 19:27           ` Larry Finger [this message]
     [not found]     ` <45A7F501.9080202@docksud.com.ar>
2007-01-12 22:59       ` evan foss
     [not found]         ` <4a55afb80701121459q4f23083t6f92a7e3bc85ccb1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-01-14  6:28           ` evan foss
     [not found]             ` <4a55afb80701132228q2e264606mf8948a45507e59ea-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-01-14 18:14               ` evan foss
2007-01-14 23:54               ` Larry Finger
2007-01-12 18:53 ` Michael Buesch
     [not found]   ` <200701121953.44630.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2007-01-12 19:18     ` evan foss
2007-01-12 19:30       ` Larry Finger
     [not found] ` <1168881379.2481.46.camel@flanders.rdu.redhat.com>
     [not found]   ` <45ABC0D5.3060008@lwfinger.net>
     [not found]     ` <4a55afb80701151502q7bf8bbabp7507a42f072efd29@mail.gmail.com>
     [not found]       ` <45AC41C4.2070401@lwfinger.net>
2007-01-18 12:52         ` evan foss

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=45A7E125.8030009@lwfinger.net \
    --to=larry.finger-tq5ms3gmjblk1umjsbkqmq@public.gmane.org \
    --cc=bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=mb-fseUSCV1ubazQB+pC5nmwQ@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).