On Monday 30 August 2010 08:33:30 Hans Petter Selasky wrote:
> Hi,
>
> Could you dump device descriptor and current configuration descriptor using
> usbconfig. I need the vendor ID and product ID at least to be able to debug
> this issue.
# usbconfig -d ugen0.2 dump_device_desc
ugen0.2: at usbus
On Monday 30 August 2010 04:18:56 Jim Bryant wrote:
> well, i can't speak for K&R 1978, as i can't currently find my copy,
> but, for a quick brush up, you might want to read pages 80 and 81 from
> K&R 2nd Ed. 1988.
>
> your idea that the preprocessor will evaluate
>
> #define thirtytwok (1<<15)
Hi,
Could you dump device descriptor and current configuration descriptor using
usbconfig. I need the vendor ID and product ID at least to be able to debug
this issue.
--HPS
On Sunday 29 August 2010 21:47:05 David Naylor wrote:
> Hi,
>
> I'm trying to get a USB webcam to work (Pixart Imaging,
but then gnu does it's own thing too. my point stands though. any
actual evaluation of thirtytwok into something OTHER THAN (1<<15) in the
actual emitted code is IMPLEMENTATION-SPECIFIC.
in the case if gnu, you do appear to be right though, in disregard to K&R.
one could also argue that my r
well, i can't speak for K&R 1978, as i can't currently find my copy,
but, for a quick brush up, you might want to read pages 80 and 81 from
K&R 2nd Ed. 1988.
your idea that the preprocessor will evaluate
#define thirtytwok (1<<15)
into 0x8000
at compile time is totally incorrect, and in fact
u.. you were saying???
8:58:44pm orb(19): cat bs3.c
#include
int main(void)
{
int toshiftornottoshift = 0x8000;
printf("%d\n", toshiftornottoshift);
return(0);
}
8:58:48pm orb(20): cc -S -O2 -o bs3.s bs3.c
8:58:53pm orb(21): cat bs3.s
.file "bs3.c"
.section.r
Hi,
I'm trying to get a USB webcam to work (Pixart Imaging, see
http://hardware4linux.info/component/12311/).
I attach the webcam and:
# dmesg
ugen0.2: at usbus0
I run webcamd (I've tried both from ports and svn):
# ./webcamd
Attached ugen0.2[0] to cuse unit 0
Creating /dev/video0
I try
Hi,
Possibly we need to add some code to check when the autoinstall system is
ready for receiving the command. What happens if you try to add a delay before
executing the eject command:
--- src/sys/dev/usb/usb_msctest.c 2010-03-08 16:57:53.0
+++ src/sys/dev/usb/usb_msctest.c
On Fri Aug 27 10, Hans Petter Selasky wrote:
> On Thursday 26 August 2010 23:50:28 Alexander Best wrote:
> > hi there,
> >
> > when i connect my mobile phone to a recent HEAD (amd64; r211393) i get the
> > following:
> >
> > ugen3.3: at usbus3
> > umass0: on usbus3
> > (probe0:umass-sim0:0:0:0)
Hi all,
Having some problems getting any EHCI devices to attach to an 8.1/amd64
machine running as a VirtualBox guest. This is VirtualBox 3.2.8 "PUEL"
edition (i.e. *not* the open-source version) running on an Ubuntu 10.04 host,
also amd64.
I have these four devices plugged in and the VM conf
On Saturday 28 August 2010 13:49:43 Matthew Luckie wrote:
> On 08/28/10 19:50, Hans Petter Selasky wrote:
> > On Saturday 28 August 2010 07:10:38 Matthew Luckie wrote:
> >> Hi
> >>
> >> I've got a 3g usb stick that works fine with 8.0-STABLE from Jan 3rd
> >> 2010, but does not with 8.1-RELEASE.
On 08/29/10 11:22, Mike Tancsa wrote:
At 07:49 AM 8/28/2010, Matthew Luckie wrote:
ugen6.2: at usbus6
umass0: on usbus6
cd1 at umass-sim0 bus 0 scbus2 target 0 lun 0
cd1: Removable CD-ROM SCSI-2 device
cd1: 40.000MB/s transfers
cd1: cd present [31484 x 2048 byte records]
Sadly no /dev/cuaU*
12 matches
Mail list logo
