mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jnf <jnf@datakill.org>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: new laptop woes
Date: Wed, 12 May 2004 10:19:07 -0500 (EST)	[thread overview]
Message-ID: <Pine.BSO.4.58.0405121014380.4366@metawire.org> (raw)
In-Reply-To: <40A1CEEF.5090309@aitel.hist.no>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Looking at other card drivers, you'll find out what a driver look like.
> You'll learn how a card driver interfaces to the kernel.
> To write a driver for this card you _need_ to know how that particular
> card is programmed. (What io adresses do it use, what do they mean,
> what are the timing requirements, and so on.)
> Looking at other drivers won't help you with that, unless one of the
> other drivers happens to use the same chips. This information is in the
> specs that broadcom so far haven't released.  Of course you can
> write to broadcom, perhaps they'll inform you when they see you
> are serious about this.

I figured as much, and I intend to use some of the other wlan drivers as a 
framework and to get a better idea of how to interface it, as for the io 
addresses/timing/etc, I was thinking that if you can use (i could be 
misremembering the name of the project) ... use the ndis wrappers and use 
an xp driver, it should be possible to just make the wrapper very verbose, 
id think anyways- although id have to look through the wrappers source and 
get a feel for how it works before i could really make that statement.
This is somewhat off topic to the discussion, but really its not- does the 
dmca restrict me from doing such a thing?

 
> The card is not assigned an irq precicely because it has no driver.
> IRQ's aren't handed out because devices exists - they are handed
> out because device drivers request them from the kernel.

i was pretty sure thats how it worked, but my level of programming in this 
specific arena is fairley minimal. Anyways, thanks for the tips/advice.

 
> Helge Hafting


jnf

- --

It is only the great men who are truly obscene.  If they had not dared to 
be obscene, they could never have dared to be great.
                -- Havelock Ellis


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (OpenBSD)

iD8DBQFAokBusKAeTAhLiCERAvEZAJ4rr9Hyz8loJhcwJ8EuhMjH6XQ4WgCfb+Pt
ljtdzfPIn2p6SCQEMahuN44=
=gDkG
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-05-12 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 16:24 jnf
2004-05-12  7:14 ` Helge Hafting
2004-05-12 15:19   ` jnf [this message]
     [not found] <A6974D8E5F98D511BB910002A50A6647615FB0B1@hdsmsx403.hd.intel.com>
2004-05-11 17:09 ` Len Brown
2004-05-12  1:37   ` jnf
2004-05-12  3:20     ` Len Brown
2004-05-13 12:55 Martin Knoblauch

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=Pine.BSO.4.58.0405121014380.4366@metawire.org \
    --to=jnf@datakill.org \
    --cc=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®