Re: d-link dwl520 wireless pci
In message: [EMAIL PROTECTED]
Brooks Davis [EMAIL PROTECTED] writes:
: If it's going to work the definition for the Linksys WMP11 will do it.
: It will have the wrong name in dmesg, but that doesn't do anything.
: This entry should be changed to reflect the fact that it's actually an
: Intersil Prism 2.5 ID that lazy vendors are using.
Comments on the following patch? It removes the extra IEEE 802.11
stuff (which is noise since wi is an 802.11b driver :-) and changes
Linksys WMP11 to the more generic Intersil Prism2.5 PCI.
Warner
Index: if_wi_pci.c
===
RCS file: /home/imp/FreeBSD/CVS/src/sys/dev/wi/if_wi_pci.c,v
retrieving revision 1.5
diff -u -r1.5 if_wi_pci.c
--- if_wi_pci.c 14 Apr 2002 22:08:58 - 1.5
+++ if_wi_pci.c 27 Apr 2002 07:06:57 -
@@ -94,13 +94,13 @@
int bus_type;
char *desc;
} pci_ids[] = {
- {0x1638, 0x1100, WI_BUS_PCI_PLX, PRISM2STA PCI WaveLAN/IEEE 802.11},
- {0x1385, 0x4100, WI_BUS_PCI_PLX, Netgear MA301 PCI IEEE 802.11b},
- {0x16ab, 0x1101, WI_BUS_PCI_PLX, GLPRISM2 PCI WaveLAN/IEEE 802.11},
- {0x16ab, 0x1102, WI_BUS_PCI_PLX, Linksys WDT11 PCI IEEE 802.11b},
- {0x1260, 0x3873, WI_BUS_PCI_NATIVE, Linksys WMP11 PCI Prism2.5},
- {0x10b7, 0x7770, WI_BUS_PCI_PLX, 3Com Airconnect IEEE 802.11b},
- {0x111a, 0x1023, WI_BUS_PCI_PLX, Siemens SpeedStream IEEE 802.11b},
+ {0x1638, 0x1100, WI_BUS_PCI_PLX, PRISM2STA PCI WaveLAN},
+ {0x1385, 0x4100, WI_BUS_PCI_PLX, Netgear MA301 PCI},
+ {0x16ab, 0x1101, WI_BUS_PCI_PLX, GLPRISM2 PCI WaveLAN},
+ {0x16ab, 0x1102, WI_BUS_PCI_PLX, Linksys WDT11 PCI},
+ {0x1260, 0x3873, WI_BUS_PCI_NATIVE, Intersil Prism2.5 PCI},
+ {0x10b7, 0x7770, WI_BUS_PCI_PLX, 3Com Airconnect},
+ {0x111a, 0x1023, WI_BUS_PCI_PLX, Siemens SpeedStream},
{0, 0, 0, NULL}
};
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
RE: d-link dwl520 wireless pci
Seems to be working just fine, appropriate portion of dmesg
wi0: Intersil Prism2.5 PCI mem 0xfb80-0xfb800fff irq 2 at device
10.0 on pci0
wi0: 802.11 address: 00:05:5d:da:5f:47
wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
wi0: Intersil Firmware: Primary 1.00.07, Station 1.03.05
Kinda unrelated I think.. But dunno it just started happening after I
ran the patch and recompiled... I have numerous machines, all 10.0.0.x
and a wireless networks 10.0.x.x My rl0 card has decided it won't
talk to .4 and the .4 machine won't talk to the .2 machine, but both of
the machines will talk to the rest of the network just fine (note I did
do a cvsup just before I ran your patch). After about 5 to 10 min they
start talking just fine.. No user interferance.. They just start to
work.. Dunno.. Prolly under wrong thread... But I figured I would throw
it out there anyways. However the wireless network works great, well no
real diff as far as I can tell.
Jason
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of M. Warner Losh
Sent: Saturday, April 27, 2002 3:08 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: d-link dwl520 wireless pci
In message: [EMAIL PROTECTED]
Brooks Davis [EMAIL PROTECTED] writes:
: If it's going to work the definition for the Linksys WMP11 will do it.
: It will have the wrong name in dmesg, but that doesn't do anything.
: This entry should be changed to reflect the fact that it's actually an
: Intersil Prism 2.5 ID that lazy vendors are using.
Comments on the following patch? It removes the extra IEEE 802.11 stuff
(which is noise since wi is an 802.11b driver :-) and changes Linksys
WMP11 to the more generic Intersil Prism2.5 PCI.
Warner
Index: if_wi_pci.c
===
RCS file: /home/imp/FreeBSD/CVS/src/sys/dev/wi/if_wi_pci.c,v
retrieving revision 1.5
diff -u -r1.5 if_wi_pci.c
--- if_wi_pci.c 14 Apr 2002 22:08:58 - 1.5
+++ if_wi_pci.c 27 Apr 2002 07:06:57 -
@@ -94,13 +94,13 @@
int bus_type;
char *desc;
} pci_ids[] = {
- {0x1638, 0x1100, WI_BUS_PCI_PLX, PRISM2STA PCI WaveLAN/IEEE
802.11},
- {0x1385, 0x4100, WI_BUS_PCI_PLX, Netgear MA301 PCI IEEE
802.11b},
- {0x16ab, 0x1101, WI_BUS_PCI_PLX, GLPRISM2 PCI WaveLAN/IEEE
802.11},
- {0x16ab, 0x1102, WI_BUS_PCI_PLX, Linksys WDT11 PCI IEEE
802.11b},
- {0x1260, 0x3873, WI_BUS_PCI_NATIVE, Linksys WMP11 PCI
Prism2.5},
- {0x10b7, 0x7770, WI_BUS_PCI_PLX, 3Com Airconnect IEEE
802.11b},
- {0x111a, 0x1023, WI_BUS_PCI_PLX, Siemens SpeedStream IEEE
802.11b},
+ {0x1638, 0x1100, WI_BUS_PCI_PLX, PRISM2STA PCI WaveLAN},
+ {0x1385, 0x4100, WI_BUS_PCI_PLX, Netgear MA301 PCI},
+ {0x16ab, 0x1101, WI_BUS_PCI_PLX, GLPRISM2 PCI WaveLAN},
+ {0x16ab, 0x1102, WI_BUS_PCI_PLX, Linksys WDT11 PCI},
+ {0x1260, 0x3873, WI_BUS_PCI_NATIVE, Intersil Prism2.5 PCI},
+ {0x10b7, 0x7770, WI_BUS_PCI_PLX, 3Com Airconnect},
+ {0x111a, 0x1023, WI_BUS_PCI_PLX, Siemens SpeedStream},
{0, 0, 0, NULL}
};
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: d-link dwl520 wireless pci
On Sat, Apr 27, 2002 at 01:07:37AM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Brooks Davis [EMAIL PROTECTED] writes: : If it's going to work the definition for the Linksys WMP11 will do it. : It will have the wrong name in dmesg, but that doesn't do anything. : This entry should be changed to reflect the fact that it's actually an : Intersil Prism 2.5 ID that lazy vendors are using. Comments on the following patch? It removes the extra IEEE 802.11 stuff (which is noise since wi is an 802.11b driver :-) and changes Linksys WMP11 to the more generic Intersil Prism2.5 PCI. Looks reasionable. You might rip out the PCI bit since the attachment bus is printed seperatly. Since all the lines are changing anyway, you might also sort it. I've been meaning to do that and haven't got arount to it. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg37781/pgp0.pgp Description: PGP signature
Re: d-link dwl520 wireless pci
* . ten tacles . . [EMAIL PROTECTED] [020426 16:03] wrote:
via cvs last night) and i couldn't find a definition of this card:
pci_ids[] = {
...
{0x1260, 0x3873, WI_BUS_PCI_NATIVE, Linksys WMP11 PCI Prism2.5},
...
pci0: unknown card (vendor=0x1260, dev=0x3873) at 11.0 irq 12
I think you mucked up your kernel install. Are you positive?
Try sticking a printf in the driver's probe routine to make sure
it's being called at boot time.
--
-Alfred Perlstein [[EMAIL PROTECTED]]
'Instead of asking why a piece of software is using 1970s technology,
start asking why software is ignoring 30 years of accumulated wisdom.'
Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: d-link dwl520 wireless pci
On Fri, Apr 26, 2002 at 07:44:11PM -0400, . ten tacles . . wrote:
recently acquired a dwl520 and i was wondering
if there is freebsd support for this card.
i looked through what appeared to be the pci-support
portion of the wi driver (if_wi_pci.c ..checked out
via cvs last night) and i couldn't find a definition of this card:
pci_ids[] = {
{0x1638, 0x1100, WI_BUS_PCI_PLX, PRISM2STA PCI WaveLAN/IEEE 802.11},
{0x1385, 0x4100, WI_BUS_PCI_PLX, Netgear MA301 PCI IEEE 802.11b},
{0x16ab, 0x1101, WI_BUS_PCI_PLX, GLPRISM2 PCI WaveLAN/IEEE 802.11},
{0x16ab, 0x1102, WI_BUS_PCI_PLX, Linksys WDT11 PCI IEEE 802.11b},
{0x1260, 0x3873, WI_BUS_PCI_NATIVE, Linksys WMP11 PCI Prism2.5},
{0x10b7, 0x7770, WI_BUS_PCI_PLX, 3Com Airconnect IEEE 802.11b},
{0x111a, 0x1023, WI_BUS_PCI_PLX, Siemens SpeedStream IEEE 802.11b},
{0, 0, 0, NULL}
this may or may not be indicative of support for this card as far as i
know (which is not much regarding driver hacking). i compiled the driver
into the kernel anyways and got this on bootup:
pci0: unknown card (vendor=0x1260, dev=0x3873) at 11.0 irq 12
so would anyone happen to know if this card is supported and if so,
is there a diff/patch/revision that i should get or procedure i should
follow?
If it's going to work the definition for the Linksys WMP11 will do it.
It will have the wrong name in dmesg, but that doesn't do anything.
This entry should be changed to reflect the fact that it's actually an
Intersil Prism 2.5 ID that lazy vendors are using.
-- Brooks
--
Any statement of the form X is the one, true Y is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
msg37753/pgp0.pgp
Description: PGP signature
RE: d-link dwl520 wireless pci
U using latest version of -current, in fact even the original 5.0 DR1
iso release supported the card, kernel needed some minor modification,
but I am using the dlink dwl 520 in my box right now without any
problems. And Brooks Davis was correct, with shows up as a linksys
device on my machines.
If the original poster wants, I can send him my kernal config file, but
I think I really only had to add options card which I think was
commented out, not too sure, it was a while back, and I had a lot of
other issues with the kernels and the machine taking a huge dump to
panic mode a lot on some other things, like smbfs and smp.
Snippet of dmesg below.
wi0: Linksys WMP11 PCI Prism2.5 mem 0xfb80-0xfb800fff irq 2 at
device 10.0 on pci0
wi0: 802.11 address: 00:05:5d:da:5f:47
wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
wi0: Intersil Firmware: Primary 1.00.07, Station 1.03.05
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Brooks Davis
Sent: Friday, April 26, 2002 8:18 PM
To: . ten tacles . .
Cc: [EMAIL PROTECTED]
Subject: Re: d-link dwl520 wireless pci
On Fri, Apr 26, 2002 at 07:44:11PM -0400, . ten tacles . . wrote:
recently acquired a dwl520 and i was wondering
if there is freebsd support for this card.
i looked through what appeared to be the pci-support
portion of the wi driver (if_wi_pci.c ..checked out
via cvs last night) and i couldn't find a definition of this card:
pci_ids[] = {
{0x1638, 0x1100, WI_BUS_PCI_PLX, PRISM2STA PCI WaveLAN/IEEE
802.11},
{0x1385, 0x4100, WI_BUS_PCI_PLX, Netgear MA301 PCI IEEE
802.11b},
{0x16ab, 0x1101, WI_BUS_PCI_PLX, GLPRISM2 PCI WaveLAN/IEEE
802.11},
{0x16ab, 0x1102, WI_BUS_PCI_PLX, Linksys WDT11 PCI IEEE
802.11b},
{0x1260, 0x3873, WI_BUS_PCI_NATIVE, Linksys WMP11 PCI
Prism2.5},
{0x10b7, 0x7770, WI_BUS_PCI_PLX, 3Com Airconnect IEEE
802.11b},
{0x111a, 0x1023, WI_BUS_PCI_PLX, Siemens SpeedStream IEEE
802.11b},
{0, 0, 0, NULL}
this may or may not be indicative of support for this card as far as i
know (which is not much regarding driver hacking). i compiled the
driver into the kernel anyways and got this on bootup:
pci0: unknown card (vendor=0x1260, dev=0x3873) at 11.0 irq 12
so would anyone happen to know if this card is supported and if so, is
there a diff/patch/revision that i should get or procedure i should
follow?
If it's going to work the definition for the Linksys WMP11 will do it.
It will have the wrong name in dmesg, but that doesn't do anything. This
entry should be changed to reflect the fact that it's actually an
Intersil Prism 2.5 ID that lazy vendors are using.
-- Brooks
--
Any statement of the form X is the one, true Y is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
