From: Dave <kilroyd@googlemail.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: Dave <kilroyd@googlemail.com>, Greg KH <greg@kroah.com>,
TJ <linux@tjworld.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Casual J. Programmer" <casualprogrammer@googlemail.com>,
linux-wireless@vger.kernel.org,
Alexander Shirshikov <alexander.shirshikov@gmail.com>
Subject: Re: Agere Hermes source-code: copyright situation
Date: Thu, 02 Oct 2008 18:44:02 +0100 [thread overview]
Message-ID: <48E50862.3030205@gmail.com> (raw)
In-Reply-To: <200810020637.27321.arvidjaar@mail.ru>
Andrey Borzenkov wrote:
>> FYI, Hermes I hardware is already covered by the orinoco driver. WPA and firmware download functionality (which is supported by the Agere driver, but not orinoco in 2.6.27) is already in the wireless queue for 2.6.28.
>>
>
> Yes, I discovered this yesterday as well. Thank you!
>
> How are you going to distribute firmware? You will need 9.x firmware from
> original Agere driver; do I understand it correctly that it will come
> with orinoco in binary form?
I was hoping we could get it into David Woodhouses firmware tree. However I haven't had a response to my original message. I'll try again with a patch.
Dave.
next prev parent reply other threads:[~2008-10-02 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200809290949.35749.arvidjaar@mail.ru>
[not found] ` <20081001031907.GA19181@kroah.com>
[not found] ` <200810011413.17059.arvidjaar@mail.ru>
[not found] ` <1222879229.17264.4.camel@hephaestion>
[not found] ` <20081001200039.GA29874@kroah.com>
2008-10-01 23:00 ` Agere Hermes source-code: copyright situation Dave
2008-10-02 2:37 ` Andrey Borzenkov
2008-10-02 17:44 ` Dave [this message]
2008-10-02 20:00 ` Greg KH
2008-10-02 20:31 ` Dan Williams
2008-10-02 20:37 ` Greg KH
2008-10-02 21:28 ` Dan Williams
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=48E50862.3030205@gmail.com \
--to=kilroyd@googlemail.com \
--cc=alexander.shirshikov@gmail.com \
--cc=arvidjaar@mail.ru \
--cc=casualprogrammer@googlemail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@tjworld.net \
/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).