Hello,
we have been testing the firmware for a week now and it seems stable.
I personally tested it also on a Linksys WRT54GL and it works both in
station and in AP modes. I collected the feedbacks that some of you
sent and it seems that the firmware now runs on these board:
- 4306, 4311, 4
On Fri, 2009-01-23 at 18:36 +0100, Francesco Gringoli wrote:
> Hello,
>
> we have been testing the firmware for a week now and it seems stable.
> I personally tested it also on a Linksys WRT54GL and it works both in
> station and in AP modes.
Did you try pushing it hard? i.e. doing a nice bi
Francesco Gringoli wrote:
> Hello,
>
> we have been testing the firmware for a week now and it seems stable. I
> personally tested it also on a Linksys WRT54GL and it works both in
> station and in AP modes. I collected the feedbacks that some of you sent
> and it seems that the firmware now runs
On Friday 23 January 2009 18:36:37 Francesco Gringoli wrote:
> Hello,
>
> we have been testing the firmware for a week now and it seems stable.
> I personally tested it also on a Linksys WRT54GL and it works both in
> station and in AP modes. I collected the feedbacks that some of you
> sent
On Friday 23 January 2009 19:01:00 Larry Finger wrote:
> The driver can certainly be coded to look for the open-source firmware
> names before trying to load vendor firmware. That way there will not
> be any confusion.
I already posted that, but in case you missed it:
http://bu3sch.de/patches/wire
On Friday 23 January 2009 19:50:37 Dan Williams wrote:
> On Fri, 2009-01-23 at 19:08 +0100, Michael Buesch wrote:
> > On Friday 23 January 2009 19:01:00 Larry Finger wrote:
> > > The driver can certainly be coded to look for the open-source firmware
> > > names before trying to load vendor firmware
On Jan 23, 2009, at 7:02 PM, Michael Buesch wrote:
> On Friday 23 January 2009 18:36:37 Francesco Gringoli wrote:
>> Hello,
>>
>> we have been testing the firmware for a week now and it seems stable.
>> I personally tested it also on a Linksys WRT54GL and it works both in
>> station and in AP mode
On Jan 23, 2009, at 7:01 PM, Larry Finger wrote:
> Francesco Gringoli wrote:
>> Hello,
>>
>> we have been testing the firmware for a week now and it seems
>> stable. I
>> personally tested it also on a Linksys WRT54GL and it works both in
>> station and in AP modes. I collected the feedbacks tha
On Friday 23 January 2009 20:18:52 Francesco Gringoli wrote:
> > Nothing. Why do we need to have different names?
> Well, I was only considering a question raised by John, we can surely
> maintain these names.
I guess I missed that. What was the question?
Note that proprietary and open firmwares
On Friday 23 January 2009 20:24:47 Francesco Gringoli wrote:
> On Jan 23, 2009, at 7:01 PM, Larry Finger wrote:
>
> > Francesco Gringoli wrote:
> >> Hello,
> >>
> >> we have been testing the firmware for a week now and it seems
> >> stable. I
> >> personally tested it also on a Linksys WRT54GL a
Francesco Gringoli wrote:
> Damn... that would be a very hard writing We do not have any 4311/2
> board: at first glance there are more condition registers whose meaning
> we do not know. Very different hardware, didn't know. Thank you for the
> feedback.
>
> By the way: is that device inside
On Jan 23, 2009, at 8:33 PM, Michael Buesch wrote:
> On Friday 23 January 2009 20:18:52 Francesco Gringoli wrote:
>>> Nothing. Why do we need to have different names?
>> Well, I was only considering a question raised by John, we can surely
>> maintain these names.
>
> I guess I missed that. What w
On Friday 23 January 2009 20:46:45 Francesco Gringoli wrote:
> -- Is using the Broadcom names for the firmware the best course of
> -- action? What if the opensource firmware files were named something
> -- like "os-ucode5.fw", etc. and b43 were coded to check for those files
> -- first? It would t
On Jan 23, 2009, at 8:37 PM, Michael Buesch wrote:
> On Friday 23 January 2009 20:24:47 Francesco Gringoli wrote:
>> On Jan 23, 2009, at 7:01 PM, Larry Finger wrote:
>>
>>> Francesco Gringoli wrote:
Hello,
we have been testing the firmware for a week now and it seems
stable. I
On Jan 23, 2009, at 6:44 PM, Brian J. Murrell wrote:
> On Fri, 2009-01-23 at 18:36 +0100, Francesco Gringoli wrote:
>> Hello,
>>
>> we have been testing the firmware for a week now and it seems stable.
>> I personally tested it also on a Linksys WRT54GL and it works both in
>> station and in AP mo
First probe for proprietary firmware and then probe for opensource firmware.
This way around it's a win-win situation.
1) If proprietary fw is available, it will work.
2) If opensource firmware is available, but no proprietary (Distros can only
ship open fw)
it might work.
3) If both open and p
Michael Buesch wrote:
> First probe for proprietary firmware and then probe for opensource firmware.
> This way around it's a win-win situation.
> 1) If proprietary fw is available, it will work.
> 2) If opensource firmware is available, but no proprietary (Distros can only
> ship open fw)
>it
On Saturday 24 January 2009 06:04:47 Larry Finger wrote:
> Michael Buesch wrote:
> > First probe for proprietary firmware and then probe for opensource firmware.
> > This way around it's a win-win situation.
> > 1) If proprietary fw is available, it will work.
> > 2) If opensource firmware is avail
18 matches
Mail list logo
