Re: make: variable expansion in .for/.endfor
# [EMAIL PROTECTED] / 2003-05-16 15:30:01 +0300:
On Sun, Apr 27, 2003 at 02:48:12PM +0200, Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2003-04-26 14:53:36 +0300:
On Fri, Apr 25, 2003 at 08:44:00PM +0200, Roman Neuhauser wrote:
Try the following makefile: it works if called with -DONE, but does not
if called with -DTWO. Should I treat it as a bug and file a PR?
LIST= foo bar baz
.if defined(ONE)
. for v in ${LIST}
.if !defined(WITHOUT_${v:U})
WITH_${v:U}=yes
.endif
. endfor
.endif
.if defined(TWO)
. for v in ${LIST}
V=${v:U}
.if !defined(WITHOUT_${V})
WITH_${V}=yes
.endif
. endfor
.endif
a:
@echo \$${WITH_FOO}: ${WITH_FOO}
@echo \$${WITH_BAR}: ${WITH_BAR}
@echo \$${WITH_BAZ}: ${WITH_BAZ}
.PHONY: a
I think this is a known bug, and it seems to even be documented
in the BUGS section of -STABLE's make(1) manual page.
I don't think this is covered. Can you point out the relevant text?
Yes, BUGS section talks about a different problem (...)
FWIW, the code snippet above works perfectly under 5.x make(1).
I recall this problem was fixed (perhaps, it was even me, not
sure). Sorry, but I don't have enough time to invest into
backporting the bugfix into RELENG_4, the latter is becoming
less priority for me as 5.x evolves.
If you'll be able to extract it from HEAD (there is a huge
backlog of non-backported fixes for make(1) there), I will
happily commit it for you.
$ uname -r
5.1-BETA
$ make -DONE
${WITH_FOO}: yes
${WITH_BAR}: yes
${WITH_BAZ}: yes
$ make -DTWO
${WITH_FOO}: yes
${WITH_BAR}: yes
${WITH_BAZ}: yes
I've spent two hours in cvsweb but haven't noticed a commit message
that would indicate a relation to this problem, and the source code
is obviously over my head.
But it looks like the problem is in the order of processing loops,
and applying modifiers... or something:
[EMAIL PROTECTED] ~ 1024:0 cat tmp/scratch4
LIST= foo bar baz
.for v in ${LIST}
V= ${v:U}
V_${v}= ${V}
v_${v}= ${v}
.endfor
all:
.for v in ${LIST}
@echo \$${V_${v}}: ${V_${v}}
.endfor
.for v in ${LIST}
@echo \$${v_${v}}: ${v_${v}}
.endfor
.PHONY: all
[EMAIL PROTECTED] ~ 1025:0 make -f tmp/scratch4
${V_foo}: BAZ
${V_bar}: BAZ
${V_baz}: BAZ
${v_foo}: foo
${v_bar}: bar
${v_baz}: baz
[EMAIL PROTECTED] ~ 1026:0 uname -a
FreeBSD freepuppy.bellavista.cz 4.8-STABLE FreeBSD 4.8-STABLE #2: Thu Jun 5
12:57:47 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FREEPUPPY2_5 i386
Does this help identifying the responsible code? I'd really like to
continue using 4.x for some time, and this bitrot in make is quite
unfortunate for me.
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message.see http://www.eyrie.org./~eagle/faqs/questions.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kqueue/kevent support in scsi device drivers
yeah, I would like to implement it in scsi_target driver. I am using scsi HBA in target to emulate as a sequential device. My userland application needs to be notified of some events taking place in scsi_target driver. Could you pls suggest me the best approach for this?? Thanks, Jaya Valentin Nechayev [EMAIL PROTECTED] wrote: Fri, May 30, 2003 at 12:14:50, jaya_bhat100 (Jayasheela Bhat) wrote about kqueue/kevent support in scsi device drivers: JB At present, kevent is supported for vnode, fifos, pipes and sockets, I believe. JB I would like to use kevent notification in scsi devices. But the drivers scsi_xx.c do not support it. Whether I can implement it in scsi device driver using KNOTE? JB I was going through tty.c where KNOTE is used. struct 'tty' has the support for it. The same is not available in struct 'disk'. JB Could anyone tell me whether it is possible to implement it and how?? What is the aim to do it? tty, sockets, pipes, fifos are sequential devices with data pushing to it. Disks are random access devices, this is the main reason why disk/filesystem read() can't be nonblocking by itself: there are two different operations in them - 1) process says to kernel what it want read, 2) kernel returns data. (And similarly for write().) To read from random access devices, AIO API was created (aio_read(), aio_write(), etc.), and it doesn't require your explicit KNOTE adding: it already supports EVFILT_AIO and SIGEV_KEVENT. If you can access something at SCSI subsystem as sequential device, let you go. But, it's better to implement KNOTE in driver of this device itself, not common SCSI layer, which is too complicated to allow it. -netch- Catch all the cricket action. Download Yahoo! Score tracker ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
PCI ID Patch for Intel Ether Express Pro 100 VE (82801BA)
Having got a new machine here a few days ago, an Intel ICH D865 PERL
board based Pentium IV machine, with an on-board Intel EtherExpress
Pro 100 VE, it failed to detect the network adapter.
Seeing that it is an EtherExpress Pro 100, I though the fxp module
should work with it, and found out that the PCI ID (8086:1050) just
isn't recognized as one (new chip or something, apparently).
With the following patch to if_fxp.c:
--- sys/dev/fxp/if_fxp.c.orig Thu Jun 12 14:08:22 2003
+++ sys/dev/fxp/if_fxp.cThu Jun 12 13:29:37 2003
@@ -162,6 +162,7 @@
{ 0x103C, Intel 82801DB (ICH4) Pro/100 Ethernet },
{ 0x103D, Intel 82801DB (ICH4) Pro/100 VE Ethernet },
{ 0x103E, Intel 82801DB (ICH4) Pro/100 VM Ethernet },
+{ 0x1050, Intel 82801BA (D865) Pro/100 VE Ethernet },
{ 0x1059, Intel 82551QM Pro/100 M Mobile Connection },
{ 0x1209, Intel 82559ER Embedded 10/100 Ethernet },
{ 0x1229, Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet },
it seems to work. I am not sure how reliable it is and whether other
modifications should be made, but it worked fine for now.
Of course, the ID string is also perhaps not the best - perhaps it
needs to be changed.
Anyway, I would like it to be added to the driver, so new machines
with that adapter will work out of the box. Should I submit this
trivial patch to anywhere else, or can it be picked up from this list?
BTW, I had the same story with Linux (that's what they wanted on it, I
was just diagnosing the problem) before, and a similar change to the
Linux eepro100 driver worked as well - had it worked with Linux out of
the box, I wouldn't probably try FreeBSD on it...
Thanks,
-- Tom
--
Tom Alsberg - hacker (being the best description fitting this space)
Web page: http://www.cs.huji.ac.il/~alsbergt/
DISCLAIMER: The above message does not even necessarily represent what
my fingers have typed on the keyboard, save anything further.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI ID Patch for Intel Ether Express Pro 100 VE (82801BA)
On Thu, 12 Jun 2003 14:14:53 +0300
Tom Alsberg [EMAIL PROTECTED] wrote:
Having got a new machine here a few days ago, an Intel ICH D865 PERL
board based Pentium IV machine, with an on-board Intel EtherExpress
Pro 100 VE, it failed to detect the network adapter.
Seeing that it is an EtherExpress Pro 100, I though the fxp module
should work with it, and found out that the PCI ID (8086:1050) just
isn't recognized as one (new chip or something, apparently).
With the following patch to if_fxp.c:
--- sys/dev/fxp/if_fxp.c.orig Thu Jun 12 14:08:22 2003
+++ sys/dev/fxp/if_fxp.cThu Jun 12 13:29:37 2003
@@ -162,6 +162,7 @@
{ 0x103C, Intel 82801DB (ICH4) Pro/100 Ethernet },
{ 0x103D, Intel 82801DB (ICH4) Pro/100 VE Ethernet },
{ 0x103E, Intel 82801DB (ICH4) Pro/100 VM Ethernet },
+{ 0x1050, Intel 82801BA (D865) Pro/100 VE Ethernet },
{ 0x1059, Intel 82551QM Pro/100 M Mobile Connection },
{ 0x1209, Intel 82559ER Embedded 10/100 Ethernet },
{ 0x1229, Intel 82557/8/9 EtherExpress Pro/100(B)
Ethernet },
it seems to work. I am not sure how reliable it is and whether other
modifications should be made, but it worked fine for now.
Of course, the ID string is also perhaps not the best - perhaps it
needs to be changed.
Anyway, I would like it to be added to the driver, so new machines
with that adapter will work out of the box. Should I submit this
trivial patch to anywhere else, or can it be picked up from this list?
You should check send-pr(1). Thanks for the contribution!
BTW, I had the same story with Linux (that's what they wanted on it, I
was just diagnosing the problem) before, and a similar change to the
Linux eepro100 driver worked as well - had it worked with Linux out of
the box, I wouldn't probably try FreeBSD on it...
Thanks,
-- Tom
--
Tom Alsberg - hacker (being the best description fitting this space)
Web page: http://www.cs.huji.ac.il/~alsbergt/
DISCLAIMER: The above message does not even necessarily represent
what my fingers have typed on the keyboard, save anything further.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
[EMAIL PROTECTED]
--
Vlad GALU
Network Administrator VipNET Bucharest
tel: 021/3039940
email: [EMAIL PROTECTED]
web: http://www.vipnet.ro
PGP: http://mirapoint.vipnet.ro/public_key.pgp
pgp0.pgp
Description: PGP signature
Re: PCI ID Patch for Intel Ether Express Pro 100 VE (82801BA)
Tom Alsberg wrote: Having got a new machine here a few days ago, an Intel ICH D865 PERL board based Pentium IV machine, with an on-board Intel EtherExpress Pro 100 VE, it failed to detect the network adapter. Seeing that it is an EtherExpress Pro 100, I though the fxp module should work with it, and found out that the PCI ID (8086:1050) just isn't recognized as one (new chip or something, apparently). Patch committed, thanks! Maxime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Fw: SAPDB FreeBSD Port Anouncement
fyi!!! - Original Message - From: Kai Mosebach [EMAIL PROTECTED] Newsgroups: gmane.comp.db.sapdb.sources Sent: Saturday, May 31, 2003 1:47 AM Subject: SAPDB FreeBSD Port Anouncement Dear all, I am pleased to announce the first working binary preview of the SAPDB 7.4.3 for FreeBSD 5.0. I would like to invite you to install it and try it out, to give me feedback and bug reporting. I would also like to know, if it is possible to run the port on FreeBSD 4.x. (You might need to replace the liblinuxthread.* files in the sapdb-lib folder then) The latest binary build can be found on Mirror #2 at : http://www.komadev.de/downloads Have fun, and please give me feedback. Regards Kai PS : Thanx to Daniel Dittmar, who was a real big help to me (and will hopefully be in future ;) ! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fw: SAPDB FreeBSD Port Anouncement
'K, I'm curious here ... is this a native port, or a linux port? the liblinuxthread.* mention here makes me think its more a linux binary running on a FreeBSD machine, but just want to clarify ... On Thu, 12 Jun 2003, Pranas Baliuka wrote: fyi!!! - Original Message - From: Kai Mosebach [EMAIL PROTECTED] Newsgroups: gmane.comp.db.sapdb.sources Sent: Saturday, May 31, 2003 1:47 AM Subject: SAPDB FreeBSD Port Anouncement Dear all, I am pleased to announce the first working binary preview of the SAPDB 7.4.3 for FreeBSD 5.0. I would like to invite you to install it and try it out, to give me feedback and bug reporting. I would also like to know, if it is possible to run the port on FreeBSD 4.x. (You might need to replace the liblinuxthread.* files in the sapdb-lib folder then) The latest binary build can be found on Mirror #2 at : http://www.komadev.de/downloads Have fun, and please give me feedback. Regards Kai PS : Thanx to Daniel Dittmar, who was a real big help to me (and will hopefully be in future ;) ! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: [EMAIL PROTECTED] secondary: [EMAIL PROTECTED]|postgresql}.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
how can I hack my com interrupt?
Hi, guys, I want to hack my com interface to specail purpose. I want to use the Modem Status Register. When the high 4 bits change, it could spring an interrupt. So, I set the Intertupt Enable Register(in sioattach fuction) to the interrupt, which support changing in the state of the modem input pins(IER_EMSC). I set the MSR successfully. But when the MSR state change, the siointr print anything(I add a printf as the first line of the function). I found there are 4 level interrupt(IIR). I want to set the IIR 4 level to support Modem status. But I couldn't set the Interrupt Identification Register, why? the code of set IIR is in the sioattach function: sio_setreg(com, com_iir, IIR_MLSC); I found the com_iir content is not changed. How can I do that? My OS is FreeBSD4.8-Release. Thanks a lot! Best Regards Ouyang Kai _ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ugen example
On Sun, 8 Jun 2003, Bernd Walter wrote: But there is lot of sample code available. Thanks I'll take a look at that. You must be doing something wrong - the values are 16bit only. Ooops...quite right. My mistake. If you have no /dev/ugen?.? then the device has no other endpoints in its current configuration. The usbctl tool mentioned above is good to check devices about their capabilities. usbctl reports quite a few end points so clearly something else is amiss. I'll have a play and see what I come up with. Do these devices just appear automatically thanks to devfs? Thanks, Andrew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ugen example
On Thu, Jun 12, 2003 at 11:30:28PM +1000, Andrew wrote: On Sun, 8 Jun 2003, Bernd Walter wrote: If you have no /dev/ugen?.? then the device has no other endpoints in its current configuration. The usbctl tool mentioned above is good to check devices about their capabilities. usbctl reports quite a few end points so clearly something else is amiss. I'll have a play and see what I come up with. Do these devices just appear automatically thanks to devfs? Not all endpoints have to be available in the current configuration. If you show me the output for your device I can tell you what is available under which condition. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ugen example
On Thu, 12 Jun 2003, Bernd Walter wrote: Not all endpoints have to be available in the current configuration. If you show me the output for your device I can tell you what is available under which condition. Thanks, output below. Andrew -- DEVICE addr 2 DEVICE descriptor: bLength=18 bDescriptorType=device(1) bcdUSB=1.00 bDeviceClass=255 bDeviceSubClass=255 bDeviceProtocol=255 bMaxPacketSize=64 idVendor=0x0743 idProduct=0x0002 bcdDevice=1 iManufacturer=0() iProduct=0() iSerialNumber=0() bNumConfigurations=1 CONFIGURATION descriptor 0: bLength=9 bDescriptorType=config(2) wTotalLength=218 bNumInterface=1 bConfigurationValue=1 iConfiguration=0() bmAttributes=80 bMaxPower=100 mA INTERFACE descriptor 0: bLength=9 bDescriptorType=interface(4) bInterfaceNumber=0 bAlternateSetting=0 bNumEndpoints=0 bInterfaceClass=255 bInterfaceSubClass=255 bInterfaceProtocol=255 iInterface=0() INTERFACE descriptor 1: bLength=9 bDescriptorType=interface(4) bInterfaceNumber=0 bAlternateSetting=1 bNumEndpoints=13 bInterfaceClass=255 bInterfaceSubClass=255 bInterfaceProtocol=255 iInterface=0() ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=1-in bmAttributes=interrupt wMaxPacketSize=16 bInterval=10 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=2-in bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=2-out bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=4-in bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=4-out bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=6-in bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=6-out bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=8-in bmAttributes=isochronous wMaxPacketSize=16 bInterval=1 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=8-out bmAttributes=isochronous wMaxPacketSize=16 bInterval=1 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=9-in bmAttributes=isochronous wMaxPacketSize=16 bInterval=1 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=9-out bmAttributes=isochronous wMaxPacketSize=16 bInterval=1 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=10-in bmAttributes=isochronous wMaxPacketSize=16 bInterval=1 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=10-out bmAttributes=isochronous wMaxPacketSize=16 bInterval=1 INTERFACE descriptor 2: bLength=9 bDescriptorType=interface(4) bInterfaceNumber=0 bAlternateSetting=2 bNumEndpoints=13 bInterfaceClass=255 bInterfaceSubClass=255 bInterfaceProtocol=255 iInterface=0() ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=1-in bmAttributes=interrupt wMaxPacketSize=64 bInterval=10 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=2-in bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=2-out bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=4-in bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=4-out bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=6-in bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=6-out bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=8-in bmAttributes=isochronous wMaxPacketSize=256 bInterval=1 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=8-out bmAttributes=isochronous wMaxPacketSize=256 bInterval=1 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=9-in bmAttributes=isochronous wMaxPacketSize=16 bInterval=1 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=9-out bmAttributes=isochronous wMaxPacketSize=16 bInterval=1 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=10-in bmAttributes=isochronous wMaxPacketSize=16 bInterval=1 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=10-out bmAttributes=isochronous wMaxPacketSize=16 bInterval=1 current configuration 1 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL
Re: ugen example
On Thu, Jun 12, 2003 at 11:47:55PM +1000, Andrew wrote: On Thu, 12 Jun 2003, Bernd Walter wrote: Not all endpoints have to be available in the current configuration. If you show me the output for your device I can tell you what is available under which condition. Thanks, output below. Andrew -- DEVICE addr 2 DEVICE descriptor: bLength=18 bDescriptorType=device(1) bcdUSB=1.00 bDeviceClass=255 bDeviceSubClass=255 bDeviceProtocol=255 bMaxPacketSize=64 idVendor=0x0743 idProduct=0x0002 bcdDevice=1 iManufacturer=0() iProduct=0() iSerialNumber=0() bNumConfigurations=1 CONFIGURATION descriptor 0: bLength=9 bDescriptorType=config(2) wTotalLength=218 bNumInterface=1 bConfigurationValue=1 iConfiguration=0() bmAttributes=80 bMaxPower=100 mA INTERFACE descriptor 0: bLength=9 bDescriptorType=interface(4) bInterfaceNumber=0 bAlternateSetting=0 bNumEndpoints=0 bInterfaceClass=255 bInterfaceSubClass=255 bInterfaceProtocol=255 iInterface=0() This is interface 0, which is used by default. It has no endpoints of it's own. Beside endpoint 0 which is always available. INTERFACE descriptor 1: bLength=9 bDescriptorType=interface(4) bInterfaceNumber=0 bAlternateSetting=1 bNumEndpoints=13 bInterfaceClass=255 bInterfaceSubClass=255 bInterfaceProtocol=255 iInterface=0() ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=1-in bmAttributes=interrupt wMaxPacketSize=16 bInterval=10 This one and the following endpoints are for interface 1. This is an alternate Interface, which means, that you can either use this or another interface - therefor ugen doesn't offer you the endpoint of interface 1 - it's not active. You have to select this interface with USB_SET_ALTINTERFACE. INTERFACE descriptor 2: bLength=9 bDescriptorType=interface(4) bInterfaceNumber=0 bAlternateSetting=2 bNumEndpoints=13 bInterfaceClass=255 bInterfaceSubClass=255 bInterfaceProtocol=255 iInterface=0() The same for Interface 2 and his endpoints. It's an alternate interface. Which one you want to use depends on your application and device. You may want to read the device documentation to select the interface which offers you the features that your application needs. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
BCM4401 ethernet driver
This is the onboard ethernet on my dell inspiron 8500 laptop and I wondered when drivers might get to freebsd. The linux kernel just imported the drivers that the broadcom wrote for it found: http://www.broadcom.com/docs/driver-download.html It doesn't appear they intend to make any freebsd drivers. Thanks in advance, James Nobis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BCM4401 ethernet driver
I am in the process of rewriting this driver for FreeBSD. It can transmit, but RX is not yet going properly. As this is evening work, it's likely to take at elast another week. This is the onboard ethernet on my dell inspiron 8500 laptop and I wondered when drivers might get to freebsd. The linux kernel just imported the drivers that the broadcom wrote for it found: http://www.broadcom.com/docs/driver-download.html It doesn't appear they intend to make any freebsd drivers. Thanks in advance, James Nobis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
MIDI testers wanted
Hello, If you have external midi hardware and Sounblaster 5.1 or a cmi soundcard, I would appreciate it if you help test out my new midi and sequencer implementation. http://www.cnd.mcgill.ca/~mat/midi2-jun1303.tgz I'm looking for .mid's that jam it up or sound wrong. You can play songs with midiplay (included, comes from netbsd) or playmidi (in the ports). --Mat -- Brain: Are you pondering what I'm pondering? Pinky: I think so Brain, but the Rockettes, it's mostly girls, isn't it? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Understanding newPCM driver
Hi I wish to teach FreeBSD (5.0-CURRENT, somewhere in mid-may, last cvsup was week ago) make use of that fancy S/P-DIF connector on my Yamaha soundcard. OTOH, I want to implement it in a Right Way (tm), so that one can choose, whether he wish to use or not to use this feature, if it's present. Which is the Right Way(tm) to add such functionality to existing newPCM driver? PS: I'm crossposting both -hackers and -current... -- Artem 'Zazoobr' Ignatjev [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
