Subject: Re: files.bluetooth:14: undefined attribute `hid'
To: None <firstname.lastname@example.org>
From: KIYOHARA Takashi <email@example.com>
Date: 09/07/2007 00:47:37
From: Iain Hibbert <firstname.lastname@example.org>
Date: Tue, 4 Sep 2007 21:08:25 +0100 (BST)
> On Tue, 4 Sep 2007, KIYOHARA Takashi wrote:
> > I found this problem. ;-)
> > The attribute 'hid' defined in files.usb. If we included files.bluetooth
> > in files.ARCH, and not include files.usb. (ex. files.hpcsh)
> > # config GENERIC
> > ../../../../dev/bluetooth/files.bluetooth:14: undefined attribute `hid'
> > ../../../../dev/bluetooth/files.bluetooth:21: undefined attribute `hid'
> > ../../../../dev/bluetooth/files.bluetooth:26: undefined attribute `hid'
> Yeah, I did notice something like that once. Does it work ok if you move
> the 'define hid' from files.usb to sys/conf/files? (as per patch)
> You still would not be able to use bthidev though, maybe the 'file
> dev/usb/hid.c hid' statement would need to be moved also?
> I got on my TODO list to move the HID stuff out of dev/usb but I got no
> time right now (good weather means fixing up boat :)
I think that bthid should move hid to dev/hid.c if it is necessary.
> > By the way, Does our bluetooth support BNEP?
> > (I want PAN ;-)
> Not yet, but something for PANU is on my list for when I get time. I think
> it can be done entirely with a userland daemon conveying packets between a
> L2CAP socket and tap(4) and should not be too much work.
I will read specifications more. (BNEP and PAN ;-)