On Fri, 20 Nov 2009 14:05:25 -0600
Larry Finger wrote:
> On 11/20/2009 01:58 PM, Chris Vine wrote:
> > On Fri, 20 Nov 2009 06:43:05 -0600
> > Larry Finger wrote:
> >> One last check. I would appreciate receiving answers to the
> >> following questions. These questions apply to anyone else with
>
On 20/11/09 10:54, Michael Buesch wrote:
Can somebody give me a genuine SPROM image for an LP-PHY card, please?
Just do this:
sudo cat $(find /sys/devices -name ssb_sprom)> ssb_sprom_copy
Does this help?
Andy
ssb_sprom_copy
Description: Binary data
__
On 11/20/2009 01:58 PM, Chris Vine wrote:
> On Fri, 20 Nov 2009 06:43:05 -0600
> Larry Finger wrote:
>> One last check. I would appreciate receiving answers to the following
>> questions. These questions apply to anyone else with this problem.
>>
>> Does the pm_qos patch help your "fatal DMA error
On Fri, 20 Nov 2009 06:43:05 -0600
Larry Finger wrote:
> One last check. I would appreciate receiving answers to the following
> questions. These questions apply to anyone else with this problem.
>
> Does the pm_qos patch help your "fatal DMA error" problem,
> particularly when booted from power-
unsubscribe me please
From: Michael Buesch
To: Larry Finger
Cc: linux-wirel...@vger.kernel.org; bcm43xx-dev@lists.berlios.de
Sent: Thu, November 19, 2009 3:13:33 PM
Subject: Re: [PATCH] ssb: Unconditionally log results of core scans
On Thursday 19 November 20
On 11/20/2009 08:11 AM, Michael Buesch wrote:
>
> I think we probably have to drop this patch and instead do a mechanism that
> fetches the sprom from userspace, if the card doesn't have one. This way we
> can have a script in userspace that generates the image based on the PCI ID
> information an
On 11/20/2009 04:36 PM, Bartłomiej Ochman wrote:
> Oncaphillis wrote:
>>
>> At least on my Acer One D250 dmidecode provides a mainboard
>> UUID.
> Who's the vendor of ethernet chip in this acer? Broadcom too?
lspci tells me its broadcom
See the lspci under
http://oncaphillis.net/lspci-aspire-d25
Larry Finger wrote:
> On 11/20/2009 05:12 AM, Michael Buesch wrote:
>
>> This patch adds a generic mechanism for overriding the SPROM mechanism
>> on devices without SPROM hardware.
>>
>> There currently is a major problem with this:
>> It tries to deduce a MAC address from various hardware pa
On 11/20/2009 08:50 AM, Ehud Gavron wrote:
> How does WL do it? Broadcom *has* to generate a MAC address that is
> both unique and in its assigned range. If we can do the same thing in
> B43 that would be ideal.
They are memory mapping a file in /etc/wlan. How this file is generated is not
known
On 11/20/2009 08:11 AM, Michael Buesch wrote:
> Ok, I think this is getting ugly :)
> The problem with all this is that if you change the harddisk, or change the
> partitioning,
> the wireless mac address would change. That would surely lead to confusion.
>
> I think we probably have to drop this
>> You might look at the "root=" part of /proc/cmdline. Mine says
>> "root=/dev/disk/by-id/ata-TOSHIBA_MK2546GSX_18C2P0KCT-part1". That disk
>> serial
>> number would certainly be unique. Even if it just said "root=/dev/sda1", it
>> would be repeatable.
>
> Ok, I think this is getting ugly :)
> Th
Hi
On Friday 20 November 2009, Larry Finger wrote:
> On 11/20/2009 05:12 AM, Michael Buesch wrote:
[...]
> You might look at the "root=" part of /proc/cmdline. Mine says
> "root=/dev/disk/by-id/ata-TOSHIBA_MK2546GSX_18C2P0KCT-part1". That disk serial
> number would certainly be unique. Even if it
On Friday 20 November 2009 15:05:39 Larry Finger wrote:
> On 11/20/2009 05:12 AM, Michael Buesch wrote:
> > This patch adds a generic mechanism for overriding the SPROM mechanism
> > on devices without SPROM hardware.
> >
> > There currently is a major problem with this:
> > It tries to deduce a M
On 11/20/2009 05:12 AM, Michael Buesch wrote:
> This patch adds a generic mechanism for overriding the SPROM mechanism
> on devices without SPROM hardware.
>
> There currently is a major problem with this:
> It tries to deduce a MAC address from various hardware parameters. But
> currently it will
Larry Finger wrote:
> One last check. I would appreciate receiving answers to the following
> questions.
> These questions apply to anyone else with this problem.
>
> Does the pm_qos patch help your "fatal DMA error" problem, particularly when
> booted from power-off?
>
> If you warm-boot after
On Thu, Nov 19, 2009 at 05:55:07PM -0600, Larry Finger wrote:
> On 11/18/2009 11:21 PM, William Bourque wrote:
> > Also, just saying, but it seems Larry's "pm_qos_update_requirement"
> > patch had some good effects; I can hardly get any connectivity without
> > it. With the patch, the wireless se
One last check. I would appreciate receiving answers to the following questions.
These questions apply to anyone else with this problem.
Does the pm_qos patch help your "fatal DMA error" problem, particularly when
booted from power-off?
If you warm-boot after loading the wl driver, does the patch
On 11/20/2009 03:29 AM, Michael Buesch wrote:
> On Friday 20 November 2009 00:55:07 Larry Finger wrote:
>>
>> If the pm_qos patch has some positive benefits, I'll push it; however, I
>> think
>> this is just a band aid, not a real fix. It also has the bad side effect of
>> keeping the CPU from goi
On 11/20/2009 04:54 AM, Michael Buesch wrote:
> On Friday 20 November 2009 11:29:20 Oncaphillis wrote:
>> Ok -- Some more details about my experience that it appears to be slow.
>
>
> Note that there are several issues. First one being the sprom calibration
> values being _wrong_ for your card. S
On Friday 20 November 2009 12:38:07 Florian Fainelli wrote:
> Why not call once random_ether_addr instead of using some kind of hash? Is it
> because you
> want the same MAC from a reboot to another?
yes.
> Ok, so for BCM63xx I would no longer have to declare my SPROM, fine.
No you still need t
This patch adds a generic mechanism for overriding the SPROM mechanism
on devices without SPROM hardware.
There currently is a major problem with this:
It tries to deduce a MAC address from various hardware parameters. But
currently it will result in the same MAC address for machines of the same
t
On Friday 20 November 2009 11:29:20 Oncaphillis wrote:
> Ok -- Some more details about my experience that it appears to be slow.
Note that there are several issues. First one being the sprom calibration
values being _wrong_ for your card. Second one is LP-PHY performance being
crappy in
general
On Fri, Nov 20, 2009 at 11:29 AM, Oncaphillis wrote:
> On 11/20/2009 10:27 AM, Michael Buesch wrote:
>> On Friday 20 November 2009 02:41:58 Oncaphillis wrote:
>>> On 11/20/2009 12:46 AM, Oncaphillis wrote:
On 11/19/2009 06:44 PM, Michael Buesch wrote:
> On Thursday 19 November 2009 16:41:
On 11/20/2009 10:27 AM, Michael Buesch wrote:
> On Friday 20 November 2009 02:41:58 Oncaphillis wrote:
>> On 11/20/2009 12:46 AM, Oncaphillis wrote:
>>> On 11/19/2009 06:44 PM, Michael Buesch wrote:
On Thursday 19 November 2009 16:41:12 Michael Buesch wrote:
> Wait, that still can't work.
On Friday 20 November 2009 00:55:07 Larry Finger wrote:
> On 11/18/2009 11:21 PM, William Bourque wrote:
> > Also, just saying, but it seems Larry's "pm_qos_update_requirement"
> > patch had some good effects; I can hardly get any connectivity without
> > it. With the patch, the wireless seems to
On Friday 20 November 2009 02:41:58 Oncaphillis wrote:
> On 11/20/2009 12:46 AM, Oncaphillis wrote:
> > On 11/19/2009 06:44 PM, Michael Buesch wrote:
> >> On Thursday 19 November 2009 16:41:12 Michael Buesch wrote:
> >>> Wait, that still can't work. I'll fix it soon...
> >>
> >> Ok, here's the upda
26 matches
Mail list logo
