From: feldmaus <feldmann_markus@gmx.de>
To: linux-wireless@vger.kernel.org
Subject: Does ACPIPHP work on my Machine
Date: Sun, 18 Jan 2009 00:20:48 +0100 [thread overview]
Message-ID: <gktp4e$p6h$1@ger.gmane.org> (raw)
Hi Matthew Garrett,
so i went home to read what you want from me to test.
The Directory </sys/bus/pci/slots/> is empty.
Si there something else i can test ?
I give you some more Information.
wes-nic:/sys/bus/pci/slots# lspci -d 14e4:4301 -vv
02:02.0 Network controller: Broadcom Corporation BCM4303 802.11b
Wireless LAN Controller (rev 02)
Subsystem: Hewlett-Packard Company Device 12f3
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 64
Interrupt: pin A routed to IRQ 17
Region 0: Memory at e0104000 (32-bit, non-prefetchable) [size=8K]
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
Regards Markus
next reply other threads:[~2009-01-17 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 23:20 feldmaus [this message]
2009-01-17 23:31 ` Does ACPIPHP work on my Machine feldmaus
2009-02-17 0:09 ` Markus Feldmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='gktp4e$p6h$1@ger.gmane.org' \
--to=feldmann_markus@gmx.de \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).