[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: kfreebsd-kernel-headers and USB API breakage



On Thu, Dec 03, 2009 at 01:09:40PM +0100, Petr Salinger wrote:
>>>> If we want to go for this solution, we have to scan the archive for
>>>> usage of this header file, and fix them by submitting a patch.
>>>
>>>> With the hope it won't come in a middle of a transition.
>>>
>>> Speaking of which, we probably shouldn't be trying too long with
>>> kfreebsd 8.0 unless we have a plan and a timeline. The blockers you
>>> mentioned make it look like we're already on people's way. So I guess
>>> it makes sense to revert ASAP and to contact -release@ once we're
>>> ready to roll.
>
> There is a new kfreebsd-kernel-headers with small fix prepared in SVN.

Thanks, I'll upload it.

> * libsdl1.2
>   builds fine with it
>
> * qemu
>   builds fine with it

Actually it still does not build fine when the patch from #558447 is
applied, which as a side effect enables USB support.

I will try to work on that and get it in the 0.12.0 release, that should
be released really soon now.

> * hal
>   There is a new upstream release 0.5.14, the git log
>   http://cgit.freedesktop.org/hal/log contains lines like
>   2009-08-18	add USB2 support
>   2009-08-18	add USB2 support to the FreeBSD backend
>
> I believe it should not be so hard to extend it for GNU/kFreeBSD.

The plan is to upload 0.5.14 asap to unstable, but the maintainer is
waiting for a fix of kfreebsd-kernel-headers or hal. Can someone work on
that?

> * freeglut
>   It is possible to disable USB scan of joystick by hack bellow.
>
> I would prefer to stay on headers based on 8.0.
>
> Petr
>
>
> --- freeglut-2.4.0.orig/src/freeglut_joystick.c
> +++ freeglut-2.4.0/src/freeglut_joystick.c
> @@ -198,6 +196,7 @@
>   */
>  static char *fghJoystickWalkUSBdev(int f, char *dev, char *out, int outlen)
>  {
> +#if 0
>    struct usb_device_info di;
>    int i, a;
>    char *cp;
> @@ -219,6 +218,7 @@
>          return out;
>        }
>    }
> +#endif
>    return NULL;
>  }
>

I don't think we should go for this kind of patch, which means one
upload to disable it, and later one more upload to enable it again.

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net


Reply to: