Larry Finger wrote:
> I think your system doesn't use PCI, so this probably won't work,
> but you should be able to implement something similar. Once you
> have a dump, you should be able to find the MAC addresses of the
> wireless and ethernet interfaces.
IIRC the WRTs don't have a sprom, instea
Michael Buesch wrote:
> > What if I configure the kernel without PCI support?
>
> I already applied the correct patch to my tree. ;)
>
> > BTW, is the SSB b44 driver/patch available somewhere?
>
> In my tree.
Oh, last time I looked it wasn't there yet, thanks. :)
--
Tobias
Matthew Garrett wrote:
> Ok, here's a patch. The stack of PCMCIA headers are needed to get the
> pcmcia_device structure. Seems to work fine for PCI - I don't have any
> PCMCIA devices. The SSB devices now appear underneath the PCI device
> rather than in the top level of /sys/devices.
What ab
Vincent Danjean wrote:
> When building this system (with a cross compiler : WRT54G is mips),
> we can choose to compile the bcm43xx module (the SoftMac one). The
> sources for this module are not patched (ie they are the same as the
> ones in 2.6.17 official linux kernel). However, I want to use m
Tobias Diedrich wrote:
> > Like I said. This makes no sense at all. Core switching is different on
> > ssb based systems. It (used to?) work(s) with the appropriate bcm64309
> > config symbol defined. However, mb and nbd are working on porting the
> > whole system code t
Alexander Tsvyashchenko wrote:
> Well, I have my access point (Asus WL-500g Deluxe, which has bcm43xx WiFi
> hardware)
> running in master mode with bcm43xx-dscape driver since April, 2006 - so
> far, no problems
> detected, so while it is indeed incomplete - it's certainly not
> "unuseable" ;-)
Johannes Berg wrote:
> Like I said. This makes no sense at all. Core switching is different on
> ssb based systems. It (used to?) work(s) with the appropriate bcm64309
> config symbol defined. However, mb and nbd are working on porting the
> whole system code to ssb which will be much nicer anyway
Hi list,
is it possible to have bcm43xx-device without CC or PCI core?
on my WRT54GL v1.1 I get the following output (2.6.17 patched to
wireless-dev as far as bcm43xx is concerned, see
http://tdiedrich.de/~ranma/kamikaze-2.6.17-wirelessdev-20061027.patch.gz):
<7>PCI: Setting latency timer of dev
Hi,
I'm willing to donate a WRT54G complete with add-on serial port for
boot-time debugging, if you are interested.
--
Tobias PGP: http://9ac7e0bc.uguu.de
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.
Michael Buesch wrote:
> On Tuesday 08 August 2006 20:22, Tobias Diedrich wrote:
> > Good catch, if I change bcm43xx_sprom_extract so that it matches the
> > one from the other driver and does not call sprom_read
> > unconditionally, then I no longer get an oops.
>
> O
Johannes Berg wrote:
> Tobias Diedrich wrote:
> >I'm trying to get the bcm43xx_d80211 driver to work on my wrt54g and
> >have so far managed to patch the wireless-dev driver into the 2.6.17
> >buildroot-ng tree, but I get the an oops (data bus error).
> >
> Um
Michael Buesch wrote:
> On Tuesday 08 August 2006 13:16, Tobias Diedrich wrote:
> > Hi,
> >
> > I'm trying to get the bcm43xx_d80211 driver to work on my wrt54g and
> > have so far managed to patch the wireless-dev driver into the 2.6.17
> > buildroot-ng
12 matches
Mail list logo
