[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: [gmane.os.netbsd.current] Re: NetBSD on the Lenovo IdeaPad S10 ?
Thanks, I'll see if I can manage to configure it.
I checked on OpenBSD and in fact, it is recognised by dmesg but defined as
"not configured". bwi is enabled in the kernel and I installed the
firmware, as described in the manpage, but the NIC does not popup.
The information given but OpenBSD are:
5:0:0: Broadcom BCM4315
0x0000: Vendor ID: 14e4 Product ID: 4315
0x0004: Command: 0006 Status ID: 0010
0x0008: Class: 02 Subclass: 80 Interface: 00 Revision: 01
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 10
0x0010: BAR mem 64bit addr: 0x00000000f0400000
0x0018: BAR empty (00000000)
0x001c: BAR empty (00000000)
0x0020: BAR empty (00000000)
0x0024: BAR empty (00000000)
0x0028: Cardbus CIS: 00000000
0x002c: Subsystem Vendor ID: 14e4 Product ID: 04b5
0x0030: Expansion ROM Base Address: 00000000
0x003c: Interrupt Pin: 01 Line: 03 Min Gnt: 00 Max Lat: 00
0x0040: Capability 0x01: Power Management
0x0058: Capability 0x09: Vendor Specific
0x00e8: Capability 0x05: Message Signaled Interrupts (MSI)
0x00d0: Capability 0x10: PCI Express
I'm gonna try modifying your patch on NetBSD and see what happens.
Le Mer 15 octobre 2008 22:49, Taylor R Campbell a écrit :
> Date: Tue, 14 Oct 2008 13:33:25 +0200 (CEST)
> From: "Joel CARNAT" <joel%carnat.net@localhost>
> nope, OpenBSD recognised it, but it is not configured:
> "Broadcom BCM4315" rev 0x01 at pci3 dev 0 function 0 not configured
> I have found the entry in pcidevs but the driver does not seem to be
> I didn't try any Linux on it.
> I ported bwi(4) to NetBSD from OpenBSD and DragonFlyBSD. It works for
> me on a PowerBook G4 with an AirPort Extreme card, which is a Broadcom
> BCM 4309 card, whose PCI product id is 0x4320. If you're brave, the
> patch is in <http://people.csail.mit.edu/riastradh/nbsd/>, and it
> applies cleanly to and builds in HEAD and netbsd-4 as of about a month
> ago. The firmware at <http://leaf.dragonflybsd.org/~sephe/bwi/v3.tbz>
> is necessary for this to operate. Furthermore, you'll need to modify
> the code in sys/dev/pci/if_bwi_pci.c so that it accepts the BCM 4315
> as well, whose product id I don't actually know -- it's not listed at
> pcidatabase.com --: you'll have to find it by grovelling through the
> PCI tree. Neither DragonFlyBSD nor OpenBSD, when I checked their
> sources out, knew about the BCM 4315; nor does the Linux bcm43xx
> driver, as far as I know.
> Caveat: I really don't know anything about the hardware you have; I am
> only guessing that it might possibly be similar to other BCM 43xx
> devices. It's up to you whether you want to risk letting the magic
> smoke out of your laptop by trying bwi(4) with your hardware; all I
> know is that bwi(4) works for me on mine. On the other hand, if you
> are a brave and enterprising soul, I'd like to know whether bwi(4)
> does anything interesting with your hardware -- even if you can't get
> packets through, I'd still like to know if, say, it claims to
> successfully load the firmware, adjust the TX power, &c.
> (Please cc me in replies, since I'm not subscribed to the list.)
Main Index |
Thread Index |