Am Montag 07 Januar 2008 schrieb Michael Buesch:
> > Still, if you can add the support for it as a feature that doesn't affect
> > the people's working configurations, no one will complain.
>
> Impossible, sorry.
> We are going to add support for new firmware, which will be needed for
> N-PHY, or w
On Sun, 06 Jan 2008 19:03:12 -0500
Pavel Roskin <[EMAIL PROTECTED]> wrote:
> Quoting "Rafael J. Wysocki" <[EMAIL PROTECTED]>:
>
> >> People don't want N-PHY support?
> >
> > Well, as it sometimes is said "the better is an enemy of the good". If they
> > feel comfortable without the N-PHY, why wo
On Monday 07 January 2008 01:12:25 Rafał Miłecki wrote:
> 2008/1/7, Michael Buesch <[EMAIL PROTECTED]>:
> > People don't want N-PHY support?
>
> Well, if your definition of people is similar to my one, they
> definitely want it! :-) I think we are just a little afraid of
> _possible_ problem with
2008/1/7, Michael Buesch <[EMAIL PROTECTED]>:
> People don't want N-PHY support?
Well, if your definition of people is similar to my one, they
definitely want it! :-) I think we are just a little afraid of
_possible_ problem with a few kernels installed at one time. Sometimes
I need to run basic k
On Mon, Jan 07, 2008 at 12:02:11AM +0100, Michael Buesch wrote:
> The _just_ wanted to tell people about a serious change _before_ it
> happens. I'm not sure why this results in all kinds of complaints.
Don't be so inhuman... :-) (For those just joining us, that is an
inside joke...)
Please don
On Monday 07 January 2008 00:51:55 Rafael J. Wysocki wrote:
> On Monday, 7 of January 2008, Michael Buesch wrote:
> > On Monday 07 January 2008 00:28:15 Rafael J. Wysocki wrote:
> > > On Monday, 7 of January 2008, Michael Buesch wrote:
> > > > On Sunday 06 January 2008 23:01:00 John W. Linville wro
Quoting "Rafael J. Wysocki" <[EMAIL PROTECTED]>:
>> People don't want N-PHY support?
>
> Well, as it sometimes is said "the better is an enemy of the good". If they
> feel comfortable without the N-PHY, why would they want it?
>
> Still, if you can add the support for it as a feature that doesn't
On Monday, 7 of January 2008, Michael Buesch wrote:
> On Monday 07 January 2008 00:28:15 Rafael J. Wysocki wrote:
> > On Monday, 7 of January 2008, Michael Buesch wrote:
> > > On Sunday 06 January 2008 23:01:00 John W. Linville wrote:
> > > > On Sun, Jan 06, 2008 at 10:38:43PM +0100, Michael Buesch
On Monday 07 January 2008 00:28:15 Rafael J. Wysocki wrote:
> On Monday, 7 of January 2008, Michael Buesch wrote:
> > On Sunday 06 January 2008 23:01:00 John W. Linville wrote:
> > > On Sun, Jan 06, 2008 at 10:38:43PM +0100, Michael Buesch wrote:
> > > > On Sunday 06 January 2008 22:35:51 Pavel Ros
On Monday, 7 of January 2008, Michael Buesch wrote:
> On Sunday 06 January 2008 23:01:00 John W. Linville wrote:
> > On Sun, Jan 06, 2008 at 10:38:43PM +0100, Michael Buesch wrote:
> > > On Sunday 06 January 2008 22:35:51 Pavel Roskin wrote:
> > > > Quoting Michael Buesch <[EMAIL PROTECTED]>:
> > >
On Sunday 06 January 2008 23:01:00 John W. Linville wrote:
> On Sun, Jan 06, 2008 at 10:38:43PM +0100, Michael Buesch wrote:
> > On Sunday 06 January 2008 22:35:51 Pavel Roskin wrote:
> > > Quoting Michael Buesch <[EMAIL PROTECTED]>:
> > >
> > > > see "fwpostfix" module parameter
> > >
> > > Can
Quoting Michael Buesch <[EMAIL PROTECTED]>:
> On Sunday 06 January 2008 22:35:51 Pavel Roskin wrote:
>> Quoting Michael Buesch <[EMAIL PROTECTED]>:
>>
>> > see "fwpostfix" module parameter
>>
>> Can we please avoid this annoyance this time?
>
> Go and complain at Broadcom please.
Mind you, there
Am Sonntag 06 Januar 2008 schrieb Michael Buesch:
> On Sunday 06 January 2008 21:34:35 John W. Linville wrote:
> > On Sun, Jan 06, 2008 at 06:02:38PM +0100, Michael Buesch wrote:
> > > This is needed in order to add support for new devices (N-PHY).
> > > Broadcom changed the ABI of the firmware, so
On Sun, Jan 06, 2008 at 10:38:43PM +0100, Michael Buesch wrote:
> On Sunday 06 January 2008 22:35:51 Pavel Roskin wrote:
> > Quoting Michael Buesch <[EMAIL PROTECTED]>:
> >
> > > see "fwpostfix" module parameter
> >
> > Can we please avoid this annoyance this time?
>
> Go and complain at Broadco
On Sunday 06 January 2008 21:34:35 John W. Linville wrote:
> On Sun, Jan 06, 2008 at 06:02:38PM +0100, Michael Buesch wrote:
>
> > This is needed in order to add support for new devices (N-PHY).
> > Broadcom changed the ABI of the firmware, so we are forced to also
> > change the ABI of the driver
On Sunday 06 January 2008 22:35:51 Pavel Roskin wrote:
> Quoting Michael Buesch <[EMAIL PROTECTED]>:
>
> > see "fwpostfix" module parameter
>
> Can we please avoid this annoyance this time?
Go and complain at Broadcom please.
--
Greetings Michael.
__
On Sun, Jan 06, 2008 at 09:58:22PM +0100, Michael Buesch wrote:
> On Sunday 06 January 2008 21:05:23 Hendrik Sattler wrote:
> > Do these firmware files go to a different directory then? I would like to
> > run
> > my current kernel (b43 from git or 2.6.24) and the new one without having
> > to
Quoting Michael Buesch <[EMAIL PROTECTED]>:
> see "fwpostfix" module parameter
Can we please avoid this annoyance this time?
It was bad at the bcm43xx/bcm43xx_mac80211 time, but it's going to be
a bigger annoyance this time, because the driver with the same name
"b43" will need a different f
On Sun, Jan 06, 2008 at 06:02:38PM +0100, Michael Buesch wrote:
> This is needed in order to add support for new devices (N-PHY).
> Broadcom changed the ABI of the firmware, so we are forced to also
> change the ABI of the driver.
Do we have reasonable confidence that the newer firmware will run
On Sunday 06 January 2008 21:05:23 Hendrik Sattler wrote:
> Am Sonntag 06 Januar 2008 schrieb Michael Buesch:
> > The b43 driver will need an incompatible firmware upgrade, soon.
> > I'm probably going to do this in 2.6.25 or 2.6.26.
> >
> > The update will require people to download and extract up
Am Sonntag 06 Januar 2008 schrieb Michael Buesch:
> The b43 driver will need an incompatible firmware upgrade, soon.
> I'm probably going to do this in 2.6.25 or 2.6.26.
>
> The update will require people to download and extract updated
> officially supported firmware. The firmware will be linked t
Ehud Gavron escribió:
> After the system has been up a while -- in this case 5 days -- the data
> transfer rate appears slow and this is confirmed by various tools such
> as ftp and speedtest.net.
>
> Reassociating with the AP has no effect on this symptom.
>
> modprobe -r b43 && modprobe b43 c
The b43 driver will need an incompatible firmware upgrade, soon.
I'm probably going to do this in 2.6.25 or 2.6.26.
The update will require people to download and extract updated
officially supported firmware. The firmware will be linked to
from the usual place at linuxwireless.org.
The driver wil
23 matches
Mail list logo