Re: USB4BSD release candidate number 3 - request for review
On Tuesday 04 November 2008, Lars Engels wrote: On Fri, Oct 31, 2008 at 05:16:09PM +, Thomas Sparrevohn wrote: On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: On Friday 31 October 2008, Olivier SMEDTS wrote: Hello, Each device driver has been splitted since RC3. Look in /boot/kernel/usb2_*. You can use modules. For example, for my usb mouse, I use usb2_input_ums. Hi, Looks like I made a small typo there. The module is named usb2_input_ms while the kernel option is named usb2_input_ums. The kernel option should be named usb2_input_ms. Is this the same issue? config: Error: device usb2_controller_uss820dci is unknown config: Error: device usb2_ethernet_dav is unknown device usb2_ethernet_dav is still unknown in the commit version in HEAD. Hi, It is going to be named usb2_ethernet_dav in the future. Currently it is named usb2_ethernet_udav . --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
On Wednesday 05 November 2008, kevin wrote: Hans Petter Selasky wrote: Hi, A new USB release is available: http://www.selasky.org/hans_petter/usb4bsd/for_review/ %md5 usb2_release_003.* MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf %sha256 usb2_release_003.* SHA256 (usb2_release_003.diff) = 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b SHA256 (usb2_release_003.tar.gz) = 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 Changes since 002 release: I try to compile kernel with usb2. Link error: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=nocona -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror vers.c ctfconvert -L VERSION vers.o linking kernel ng_ubt2.o(.text+0x38): In function `ubt_detach': : undefined reference to `ng_rmnode_self' ng_ubt2.o(.text+0x488): In function `ubt_attach': : undefined reference to `ng_make_node_common' ng_ubt2.o(.text+0x4be): In function `ubt_attach': : undefined reference to `ng_name_node' ng_ubt2.o(.text+0x52b): In function `ubt_attach': : undefined reference to `ng_unref_node' ng_ubt2.o(.text+0xc02): In function `ubt_modevent': : undefined reference to `ng_newtype' ng_ubt2.o(.text+0xde0): In function `ubt_bulk_read_complete': : undefined reference to `ng_package_data' ng_ubt2.o(.text+0xdfb): In function `ubt_bulk_read_complete': : undefined reference to `ng_address_hook' ng_ubt2.o(.text+0xe39): In function `ubt_bulk_read_complete': : undefined reference to `ng_snd_item' ng_ubt2.o(.text+0xfce): In function `ubt_intr_read_complete': : undefined reference to `ng_package_data' ng_ubt2.o(.text+0xfe9): In function `ubt_intr_read_complete': : undefined reference to `ng_address_hook' ng_ubt2.o(.text+0x1027): In function `ubt_intr_read_complete': : undefined reference to `ng_snd_item' ng_ubt2.o(.text+0x105d): In function `ng_ubt_rcvdata': : undefined reference to `ng_free_item' ng_ubt2.o(.text+0x10a7): In function `ng_ubt_rcvdata': : undefined reference to `ng_free_item' ng_ubt2.o(.text+0x124e): In function `ng_ubt_rcvmsg': : undefined reference to `ng_free_item' ng_ubt2.o(.text+0x12b3): In function `ng_ubt_rcvmsg': : undefined reference to `ng_free_item' ng_ubt2.o(.text+0x12bf): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x1314): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x1413): In function `ng_ubt_rcvmsg': : undefined reference to `ng_address_ID' ng_ubt2.o(.text+0x142a): In function `ng_ubt_rcvmsg': : undefined reference to `ng_snd_item' ng_ubt2.o(.text+0x1480): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x1561): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x162e): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x1a7a): In function `ng_ubt_shutdown': : undefined reference to `ng_unref_node' ng_ubt2.o(.text+0x1ab5): In function `ng_ubt_shutdown': : undefined reference to `ng_make_node_common' ng_ubt2.o(.text+0x1acc): In function `ng_ubt_shutdown': : undefined reference to `ng_name_node' ng_ubt2.o(.text+0x1b6b): In function `ng_ubt_shutdown': : undefined reference to `ng_unref_node' ng_ubt2.o(.text+0x1c28): In function `ubt_isoc_read_complete': : undefined reference to `ng_package_data' ng_ubt2.o(.text+0x1c43): In function `ubt_isoc_read_complete': : undefined reference to `ng_address_hook' ng_ubt2.o(.text+0x1d01): In function `ubt_isoc_read_complete': : undefined reference to `ng_snd_item' ng_ubt2.o(.text+0x1eaf): In function `ubt_bulk_read_callback': : undefined reference to `ng_send_fn' ng_ubt2.o(.text+0x20cd): In function `ubt_intr_read_callback': : undefined reference to `ng_send_fn' ng_ubt2.o(.text+0x242c): In function `ubt_isoc_read_callback': : undefined reference to `ng_send_fn' ng_ubt2.o(.text+0xc36): In function `ubt_modevent': : undefined reference to `ng_rmtype' ng_ubt2.o(.rodata+0x5f0): undefined reference to `ng_parse_uint16_type' ng_ubt2.o(.rodata+0x618): undefined reference to `ng_parse_uint16_type' ng_ubt2.o(.rodata+0x6c0): undefined reference to `ng_parse_struct_type' ng_ubt2.o(.rodata+0x700): undefined reference to
Re: USB4BSD release candidate number 3 - request for review
On Wednesday 05 November 2008, Lars Engels wrote: Hi Lars, Now I just removed everything but usb2_core from the kernel config and load the modules manually. So far it runs pretty good. Mounting a umass device, removing it and doing an 'ls' on the mountpoint freezes the system, I thought this should not happen with the new stack? It is not a USB problem. It is the CAM layer that is hanging on the disk. sysctl hw.usb2.uscanner.uscanner: 0 Could it be that this should be debug? Fixed in P4 now. Will soon sync my private SVN. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
Hi, And one last thing: # usbdevs -v usbdevs: no USB controllers found That command is no longer supported. Use usbconfig instead. I'm not sure if it is currently installed by default. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
On Tuesday 04 November 2008, Lars Engels wrote: On Tue, Nov 04, 2008 at 07:56:47PM -0200, Renato Botelho wrote: On Tue, Nov 4, 2008 at 7:22 PM, Lars Engels [EMAIL PROTECTED] wrote: On Fri, Oct 31, 2008 at 05:16:09PM +, Thomas Sparrevohn wrote: On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: On Friday 31 October 2008, Olivier SMEDTS wrote: Hello, Each device driver has been splitted since RC3. Look in /boot/kernel/usb2_*. You can use modules. For example, for my usb mouse, I use usb2_input_ums. Hi, Looks like I made a small typo there. The module is named usb2_input_ms while the kernel option is named usb2_input_ums. The kernel option should be named usb2_input_ms. Is this the same issue? config: Error: device usb2_controller_uss820dci is unknown config: Error: device usb2_ethernet_dav is unknown device usb2_ethernet_dav is still unknown in the commit version in HEAD. I believe it was just a typo, the correct is usb2_ethernet_udav Good point. :) After changing it to _udav I am getting this: In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, from /usr/src/sys/dev/usb2/sound/uaudio2.c:79: /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No such file or directory /usr/src/sys/dev/usb2/sound/uaudio2.c:81:23: error: feeder_if.h: No such file or directory In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, from /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:31: /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No such file or directory /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:36:22: error: mixer_if.h: No such file or directory mkdep: compile failed Hi, Dependancy towards device sound I think. Try loading the module instead of having the device in the kernel. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
In message: [EMAIL PROTECTED] Hans Petter Selasky [EMAIL PROTECTED] writes: : On Wednesday 05 November 2008, Lars Engels wrote: : : Hi Lars, : : Now I just removed everything but usb2_core from the kernel config and : load the modules manually. So far it runs pretty good. : : Mounting a umass device, removing it and doing an 'ls' on the mountpoint : freezes the system, I thought this should not happen with the new stack? : : It is not a USB problem. It is the CAM layer that is hanging on the disk. Sure it is CAM layer and not buffer cache or filesystem code? Warner ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
On Wed, Nov 05, 2008 at 02:18:17AM -0700, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Hans Petter Selasky [EMAIL PROTECTED] writes: : On Wednesday 05 November 2008, Lars Engels wrote: : Mounting a umass device, removing it and doing an 'ls' on the mountpoint : freezes the system, I thought this should not happen with the new stack? : : It is not a USB problem. It is the CAM layer that is hanging on the disk. Sure it is CAM layer and not buffer cache or filesystem code? Well, the CAM layer problem will immediately first - it does not like CAM busses disappearing. Once this is fixed or avoided and the problem still shows up, we can blame buffer cache / filesystem code. As I suggested before, a good fix is to create one CAM bus per USB root hub, and use that to attach all umass devices to. This will also get rid of the one-bus-per-umass-device which is visually unappealling. Regards, Rink -- Rink P.W. Springer- http://rink.nu Anyway boys, this is America. Just because you get more votes doesn't mean you win. - Fox Mulder ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
Hans Petter Selasky wrote: On Wednesday 05 November 2008, kevin wrote: Hans Petter Selasky wrote: Hi, A new USB release is available: http://www.selasky.org/hans_petter/usb4bsd/for_review/ %md5 usb2_release_003.* MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf %sha256 usb2_release_003.* SHA256 (usb2_release_003.diff) = 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b SHA256 (usb2_release_003.tar.gz) = 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 Changes since 002 release: I try to compile kernel with usb2. Hi, Try to load the module instead of having bluetooth in the kernel. Then all dependancies are loaded automatically. Depends on some bluetooth stuff. --HPS I build kernel without usb2_bluetooth_ng successfully. i notice that fingerpring and bluetooth mouse nolonger work now. in dmesg: ugen0.2: Broadcom Corp at usbus0 ugen0.3: STMicroelectronics at usbus0 maybe /etc/rc.d/bthidd and fprint package need update now. Thanks, kevin ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
On Wednesday 05 November 2008 08:15:52 Hans Petter Selasky wrote: Hi, And one last thing: # usbdevs -v usbdevs: no USB controllers found That command is no longer supported. Use usbconfig instead. I'm not sure if it is currently installed by default. --HPS usbconfig does not install per default - it does not even seem to compile - ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
In message: [EMAIL PROTECTED] kevin [EMAIL PROTECTED] writes: : Hans Petter Selasky wrote: : On Wednesday 05 November 2008, kevin wrote: : : Hans Petter Selasky wrote: : : Hi, : : A new USB release is available: : : http://www.selasky.org/hans_petter/usb4bsd/for_review/ : : %md5 usb2_release_003.* : MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 : MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf : %sha256 usb2_release_003.* : SHA256 (usb2_release_003.diff) = : 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b : SHA256 (usb2_release_003.tar.gz) = : 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 : : Changes since 002 release: : : I try to compile kernel with usb2. : : : Hi, : : Try to load the module instead of having bluetooth in the kernel. Then all : dependancies are loaded automatically. : : Depends on some bluetooth stuff. : : --HPS : : : I build kernel without usb2_bluetooth_ng successfully. i notice that : fingerpring and bluetooth mouse nolonger work now. : in dmesg: : ugen0.2: Broadcom Corp at usbus0 : ugen0.3: STMicroelectronics at usbus0 : maybe /etc/rc.d/bthidd and fprint package need update now. Almost certainly... And they will likely have to deal with both stacks for a while... Warner ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
In message: [EMAIL PROTECTED] Rink Springer [EMAIL PROTECTED] writes: : On Wed, Nov 05, 2008 at 02:18:17AM -0700, M. Warner Losh wrote: : In message: [EMAIL PROTECTED] : Hans Petter Selasky [EMAIL PROTECTED] writes: : : On Wednesday 05 November 2008, Lars Engels wrote: : : Mounting a umass device, removing it and doing an 'ls' on the mountpoint : : freezes the system, I thought this should not happen with the new stack? : : : : It is not a USB problem. It is the CAM layer that is hanging on the disk. : : Sure it is CAM layer and not buffer cache or filesystem code? : : Well, the CAM layer problem will immediately first - it does not like : CAM busses disappearing. Once this is fixed or avoided and the problem : still shows up, we can blame buffer cache / filesystem code. : : As I suggested before, a good fix is to create one CAM bus per USB root : hub, and use that to attach all umass devices to. This will also get rid : of the one-bus-per-umass-device which is visually unappealling. That might work. It might also be useful to see if the DragonFly patches to allow this port over or not... Warner ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
On Wednesday 05 November 2008, M. Warner Losh wrote: In message: [EMAIL PROTECTED] : It is not a USB problem. It is the CAM layer that is hanging on the disk. Sure it is CAM layer and not buffer cache or filesystem code? No, I'm not sure, except it is not an USB problem. I currently keep the CAM instance around after that the device has been removed from USB, returning an error on all subsequent SCSI requests. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
On Wednesday 05 November 2008, Rink Springer wrote: On Wed, Nov 05, 2008 at 02:18:17AM -0700, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Hans Petter Selasky [EMAIL PROTECTED] writes: : On Wednesday 05 November 2008, Lars Engels wrote: : Mounting a umass device, removing it and doing an 'ls' on the : mountpoint freezes the system, I thought this should not happen with : the new stack? : : It is not a USB problem. It is the CAM layer that is hanging on the : disk. Sure it is CAM layer and not buffer cache or filesystem code? Well, the CAM layer problem will immediately first - it does not like CAM busses disappearing. Once this is fixed or avoided and the problem still shows up, we can blame buffer cache / filesystem code. As I suggested before, a good fix is to create one CAM bus per USB root hub, and use that to attach all umass devices to. This will also get rid of the one-bus-per-umass-device which is visually unappealling. I've temporarily created one CAM bus per module, and release it when the usb2_storage_mass module is unloaded. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
On Wednesday 05 November 2008, kevin wrote: Hans Petter Selasky wrote: On Wednesday 05 November 2008, kevin wrote: Hans Petter Selasky wrote: Hi, A new USB release is available: http://www.selasky.org/hans_petter/usb4bsd/for_review/ %md5 usb2_release_003.* MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf %sha256 usb2_release_003.* SHA256 (usb2_release_003.diff) = 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b SHA256 (usb2_release_003.tar.gz) = 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 Changes since 002 release: I try to compile kernel with usb2. Hi, Try to load the module instead of having bluetooth in the kernel. Then all dependancies are loaded automatically. Depends on some bluetooth stuff. --HPS I build kernel without usb2_bluetooth_ng successfully. i notice that fingerpring and bluetooth mouse nolonger work now. in dmesg: ugen0.2: Broadcom Corp at usbus0 ugen0.3: STMicroelectronics at usbus0 maybe /etc/rc.d/bthidd and fprint package need update now. Try: kldload usb2_bluetooth_ng Or add: usb2_bluetooth_load=YES usb2_bluetooth_ng_load=YES to: /boot/loader.conf --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
On Wednesday 05 November 2008, [EMAIL PROTECTED] wrote: Thomas Sparrevohn [EMAIL PROTECTED] writes: On Wednesday 05 November 2008 08:15:52 Hans Petter Selasky wrote: Hi, And one last thing: # usbdevs -v usbdevs: no USB controllers found That command is no longer supported. Use usbconfig instead. I'm not sure if it is currently installed by default. --HPS usbconfig does not install per default - it does not even seem to compile - I think this patch might be a workaround then. Hi, I will get this patch in next time an USB2 update gets committed to FreeBSD-current. Thanks! --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
Thomas Sparrevohn [EMAIL PROTECTED] writes:
On Wednesday 05 November 2008 08:15:52 Hans Petter Selasky wrote:
Hi,
And one last thing:
# usbdevs -v
usbdevs: no USB controllers found
That command is no longer supported. Use usbconfig instead. I'm not sure
if
it is currently installed by default.
--HPS
usbconfig does not install per default - it does not even seem to compile -
I think this patch might be a workaround then.
Index: share/man/man4/Makefile
===
--- share/man/man4/Makefile (revision 184644)
+++ share/man/man4/Makefile (working copy)
@@ -416,6 +416,20 @@
ural.4 \
urio.4 \
usb.4 \
+ usb2_bluetooth.4 \
+ usb2_controller.4 \
+ usb2_core.4 \
+ usb2_ethernet.4 \
+ usb2_image.4 \
+ usb2_input.4 \
+ usb2_misc.4 \
+ usb2_ndis.4 \
+ usb2_quirk.4 \
+ usb2_serial.4 \
+ usb2_sound.4 \
+ usb2_storage.4 \
+ usb2_template.4 \
+ usb2_wlan.4 \
uscanner.4 \
uslcom.4 \
utopia.4 \
Index: usr.sbin/Makefile
===
--- usr.sbin/Makefile (revision 184644)
+++ usr.sbin/Makefile (working copy)
@@ -181,6 +181,7 @@
trpt \
tzsetup \
ugidfw \
+ ${_usbconfig} \
${_usbdevs} \
${_vidcontrol} \
vipw \
@@ -401,6 +402,7 @@
.endif
.if ${MK_USB} != no
+_usbconfig=usbconfig
_usbdevs= usbdevs
.endif
Index: lib/Makefile
===
--- lib/Makefile(revision 184644)
+++ lib/Makefile(working copy)
@@ -38,7 +38,8 @@
${_libpmc} libproc librt ${_libsdp} ${_libsm} ${_libsmb} \
${_libsmdb} \
${_libsmutil} libstand ${_libtelnet} ${_libthr} libthread_db libufs \
- libugidfw ${_libusbhid} ${_libvgl} libwrap liby libz ${_bind}
+ libugidfw ${_libusb20} ${_libusbhid} ${_libvgl} libwrap liby libz \
+ ${_bind}
.if exists(${.CURDIR}/csu/${MACHINE_ARCH}-elf)
_csu=csu/${MACHINE_ARCH}-elf
@@ -135,6 +136,7 @@
.endif
.if ${MK_USB} != no
+_libusb20= libusb20
_libusbhid=libusbhid
.endif
Index: lib/libusb20/Makefile
===
--- lib/libusb20/Makefile (revision 184644)
+++ lib/libusb20/Makefile (working copy)
@@ -18,7 +18,7 @@
INCS+= libusb20_compat10.h
MAN= libusb20.3
MKLINT=no
+CFLAGS+= -I${.CURDIR}/../../sys
NOGCCERROR=
.include bsd.lib.mk
-
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
Hans Petter Selasky wrote: On Wednesday 05 November 2008, kevin wrote: Hans Petter Selasky wrote: On Wednesday 05 November 2008, kevin wrote: Hans Petter Selasky wrote: Hi, A new USB release is available: http://www.selasky.org/hans_petter/usb4bsd/for_review/ %md5 usb2_release_003.* MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf %sha256 usb2_release_003.* SHA256 (usb2_release_003.diff) = 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b SHA256 (usb2_release_003.tar.gz) = 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 Changes since 002 release: I try to compile kernel with usb2. Hi, Try to load the module instead of having bluetooth in the kernel. Then all dependancies are loaded automatically. Depends on some bluetooth stuff. --HPS I build kernel without usb2_bluetooth_ng successfully. i notice that fingerpring and bluetooth mouse nolonger work now. in dmesg: ugen0.2: Broadcom Corp at usbus0 ugen0.3: STMicroelectronics at usbus0 maybe /etc/rc.d/bthidd and fprint package need update now. Try: kldload usb2_bluetooth_ng Or add: usb2_bluetooth_load=YES usb2_bluetooth_ng_load=YES to: /boot/loader.conf usb2_bluetooth was built into kernel already,and usb2_bluetooth_ng was included in ng_ubt. in /boot/loader.conf ng_ubt_load=YES usb2_bluetooth_fw_load=YES ubtbcmfw=YES Thanks, kevin ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
