Sorry for again posting something OT, but I think the result of this
discussion will in the end provide valuable input to a lot of driver
authors.
On Sun, Aug 07, 2005 at 05:01:34PM +0200, Harald Welte wrote:
> On Sun, Aug 07, 2005 at 10:32:07AM +0300, Kalle Valo wrote:
> > Harald Welte <[EMAIL PR
On Fri, Aug 12, 2005 at 12:37:55AM -0700, Chris Wedgwood wrote:
> On Sun, Aug 07, 2005 at 05:01:34PM +0200, Harald Welte wrote:
>
> > I will consult my legal counsel about this. My current naive
> > position on this is that only the actuall process of the
> > re-engineering matters, not the resul
On Sun, Aug 07, 2005 at 05:01:34PM +0200, Harald Welte wrote:
> I will consult my legal counsel about this. My current naive
> position on this is that only the actuall process of the
> re-engineering matters, not the result.
Which countries is this advice valid for? Does someone need to chase
On Sun, Aug 07, 2005 at 10:32:07AM +0300, Kalle Valo wrote:
> Harald Welte <[EMAIL PROTECTED]> writes:
>
> > I don't want to turn this list into a list of legal discussion, but
> > since I'm heavily dealing with exactly those issues during my
> > gpl-violations.org efforts, I thought I share some
Harald Welte <[EMAIL PROTECTED]> writes:
> I don't want to turn this list into a list of legal discussion, but
> since I'm heavily dealing with exactly those issues during my
> gpl-violations.org efforts, I thought I share some of the facts.
Thanks for your answer, it cleared up things. I also do
On Sat, Aug 06, 2005 at 04:53:08PM -0400, Jeff Garzik wrote:
>
> It is certainly preferred that someone write a document describing the
> hardware, and then a totally separate team write the driver, based on
> that document.
No question to that. However, I think it largely depends on _where_ the
Kalle Valo <[EMAIL PROTECTED]> wrote:
|
| This is great news. An open source Atheros driver which could be
| included to Linux is really needed.
|
| But how was the reverse engineering done? I noticed that forcedeth
| driver was implemented using the clean room design[1] and Linux
| Broadcom 4301
It is certainly preferred that someone write a document describing the
hardware, and then a totally separate team write the driver, based on
that document.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majord
Mateusz Berezecki <[EMAIL PROTECTED]> writes:
> The driver is not yet fully working because I didn't finish kernel
> integration yet. Almost all
> driver I/O ops are reverse engineered independently of openbsd openhal
> which is missing just too much.
>
>
> Ok, enough talking. Most of the atheros
On 8/5/05, Jeff Garzik <[EMAIL PROTECTED]> wrote:
> There is no document describing the API AFAIK.
>
> The best thing to do is read over the ipw2[12]00 drivers.
>
> Jeff
Ok, thanks for pointing me there.
best
Mateusz
-
To unsubscribe from this list: send the line "unsubscribe netdev"
Mateusz Berezecki wrote:
And regarding that ieee80211 API, I would be very excited if
anyone could explain the general overview of how new wireless
API works. I read the source but sometimes a quick answer from
experienced kernel coder would do more good.
There is no document describing the A
On 09:46 Fri 05 Aug , Bryan O'Sullivan wrote:
> On Fri, 2005-08-05 at 04:55 +0200, Mateusz Berezecki wrote:
>
> How far from working is it? I have a miniPCI Atheros card and would be
> interested in helping out with bringing the driver up, but it would be
> good to know what to expect first :
Mateusz Berezecki wrote:
Hi list members,
I just post the code for review for anyone interested.
I would be more than pleased to hear some feedback from you on the code.
Im sending a series of 8 patches splitted and diffed as in
SubmittingPatches documentation.
The driver is not yet fully wo
On Fri, 2005-08-05 at 04:55 +0200, Mateusz Berezecki wrote:
> The driver is not yet fully working because I didn't finish kernel
> integration yet.
How far from working is it? I have a miniPCI Atheros card and would be
interested in helping out with bringing the driver up, but it would be
good
Hi.
Mateusz Berezecki wrote:
> Im sending a series of 8 patches splitted and diffed as in
> SubmittingPatches documentation.
Patch 4/8 is missing here.
Bye, Mike
--
Use PGP/GPG!
My key: http://keys.indymedia.org/cgi-bin/lookup?op=get&search=62C29B94
Fingerprint: BC2E 79BF 0C8F 0282 864B 9CEC 83
Hi list members,
I just post the code for review for anyone interested.
I would be more than pleased to hear some feedback from you on the code.
Im sending a series of 8 patches splitted and diffed as in
SubmittingPatches documentation.
The driver is not yet fully working because I didn't fin
16 matches
Mail list logo
