From: Gianni Tedesco <gianni@scaramanga.co.uk>
To: public@mikl.as
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux Incompatibility List
Date: Sun, 29 Aug 2004 04:21:41 +0100 [thread overview]
Message-ID: <1093749701.7064.37.camel@sherbert> (raw)
In-Reply-To: <200408282143.05304.public@mikl.as>
[-- Attachment #1: Type: text/plain, Size: 2694 bytes --]
On Sat, 2004-08-28 at 21:42 -0400, Andrew Miklas wrote:
> (Sorry for the long delay...)
Thats OK.
> Yeah, we tried that at first too (actually, we were using Frank Cornelis'
> patches to Bochs). The problem with dumping all the PCI activity (even while
> the interface isn't sending/receiving) is that there is a huge amount of data
> to sift through. Even capturing for just a for a few seconds generates
> megabytes of data. You also have to deal with various events (like the
> watchdog timer) going off at random times and getting mixed in with the
> send/receive data. We also found DMA a little tricky too (ie. you need to
> dump out any data that the chip will bus-master to itself to see how it is
> structured).
OK, exactly which drivers were you using to do this? When I had the
interface brought up in win2k-server with the bcmwl5.sys driver I was
seeing every few hundred milliseconds a batch of say 12 2-byte reads on
the register space to check status...
> Also, we figured it would cause problems for supporting the whole range of
> devices that can be handled by the wl.o drivers. For example, from looking
> at the module, we can see that the driver will have somewhat different
> behaviour according to exactly what MAC and radio chips are present, the
> interface being used (ie. PCI, cardbus, etc.), the vendor, model number, and
> revision of the board itself, the contents of the ROM, etc. We decided that
> there was simply too many combinations to make the data capture approach
> useful over the entire range of Broadcom hardware, unless you repeat the
> process on every variation.
Hrm, you're sure those variations aren't trivial? Although theres lots
of checks, I would have thought they would just be stuff like "card A
supports X, Y and Z features"?
The approach that makes the most sense to me is get 1 card working to
the point where it sends/receives packets, then look at the binaries to
see what the variations are, and how they apply to what cards and just
go fill in the blanks...
> > Anyway, perhaps once I've had some time to make a little more progress
> > we would be able to compare some notes?
>
> Sure, let me know when you're ready.
I just need to improve logging support in my pciproxy patch and setup a
2nd machine with a working wireless card, then I can start in earnest.
Also, you mention DMA and sending/receiving packets, exactly how much
progress have you made so far?
--
// Gianni Tedesco (gianni at scaramanga dot co dot uk)
lynx --source www.scaramanga.co.uk/scaramanga.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-29 3:23 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 19:41 Linux Incompatibility List David N. Welton
2004-08-21 20:16 ` Joseph Pingenot
2004-08-21 20:20 ` Wakko Warner
2004-08-21 20:31 ` Lee Revell
2004-08-21 20:51 ` Wakko Warner
2004-08-21 21:06 ` Jan-Benedict Glaw
2004-08-21 21:11 ` Lee Revell
2004-08-21 21:16 ` Lee Revell
2004-08-22 14:30 ` Tonnerre
2004-08-22 14:45 ` Michael Buesch
2004-08-24 15:17 ` Jan-Benedict Glaw
2004-08-24 17:41 ` Michael Buesch
2004-08-21 21:18 ` Francois Romieu
2004-08-21 22:01 ` Wakko Warner
2004-08-21 23:53 ` Andrew Miklas
2004-08-23 3:54 ` Gianni Tedesco
2004-08-25 5:59 ` Andrew Miklas
2004-08-25 7:21 ` Gianni Tedesco
2004-08-29 1:42 ` Andrew Miklas
2004-08-29 3:21 ` Gianni Tedesco [this message]
2004-08-29 21:04 ` Andrew Miklas
2004-08-22 5:29 ` Jonathan Bastien-Filiatrault
2004-08-22 1:56 ` James Courtier-Dutton
2004-08-22 6:36 ` Jonathan Bastien-Filiatrault
2004-08-22 4:15 ` Kyle Moffett
2004-08-22 5:58 ` Lee Revell
2004-08-22 8:05 ` Geert Uytterhoeven
2004-08-22 12:07 ` R. J. Wysocki
2004-08-22 12:32 ` Gene Heskett
2004-08-24 21:30 ` Hamie
2004-08-22 15:25 ` Tonnerre
2004-08-22 11:10 ` Alan Cox
2004-08-22 12:42 ` Dave Jones
2004-08-23 6:31 ` Eric W. Biederman
2004-08-21 21:20 ` David N. Welton
2004-08-21 22:03 ` Wakko Warner
2004-08-22 0:18 ` Rutger Nijlunsing
2004-08-21 20:22 ` David N. Welton
2004-08-22 11:14 ` Alan Cox
2004-08-22 15:08 ` Joseph Pingenot
2004-08-22 20:48 ` David N. Welton
2004-08-22 20:45 ` Alan Cox
2004-08-23 20:45 ` cliff white
[not found] ` <200408221045.29316.mbuesch@freenet.de>
2004-08-22 20:34 ` David N. Welton
2004-08-22 21:24 ` David N. Welton
2004-08-25 7:41 ` Helge Hafting
2004-08-25 7:49 ` David N. Welton
2004-08-31 7:28 ` Helge Hafting
2004-08-31 10:21 ` David N. Welton
-- strict thread matches above, loose matches on Subject: below --
2004-08-22 4:19 linux
2004-08-22 13:05 ` Wakko Warner
2004-08-22 16:43 ` Horst von Brand
2004-08-22 22:42 ` Robin Rosenberg
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=1093749701.7064.37.camel@sherbert \
--to=gianni@scaramanga.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=public@mikl.as \
/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