Re: libusb and hal

Hi,

I'm also very interested in how this turns out and am willing to do some
testing upon request.

I have seen the same failure where syncing works the first time after boot,
but intermittently there after.  I have a Fedora 7 machine that is kept
consistently up to date with all patches, including the kernel.  Currently,
here is my version info as reported by rpm:

  bash-3.2$ rpm -q hal
  hal-0.5.9-8.fc7
  bash-3.2$ rpm -q kernel
  kernel-2.6.22.9-91.fc7
  bash-3.2$ uname -a
  Linux hungover.domain.com 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT
2007 x86_64 x86_64 x86_64 GNU/Linux
  bash-3.2$

Thanks,
Brent

On 10/10/07, Tom Billiet <[email protected]> wrote:
>
>
>
> ----- Original Message -----
> From: Matt Davey
> Time: 10-10-07 11:21
> > On Tue, 2007-10-09 at 21:43 -0400, R. Drew Davis wrote:
> >> On Tue, 2007-10-09 at 19:58 +0200, Tom Billiet wrote:
> >>> ----- Original Message -----
> >>> From: Matt Davey
> >>> Time: 09-10-07 19:32
> >>>> Tom,
> >>>>
> >>>> Thanks for your work on this already.  Are you saying that the
> >>>> "usb_device" is only added once, even if you disconnect the z22
> >>>> physically from your computer?
> >>> Exactly.
> >>> I must say I have not tried if there is some timeout on this, that it
> >>> will disappear after a time. But even then you would not be able to
> sync
> >>> between the timeouts.
> >>>
> >> I don't know beans about USB, but thinking about what you've described
> >> in this series of e-mails, it seems to me that you need to beware of
> the
> >> case of HAL remembering a Palm device that was formerly attached but is
> >> no longer there.   That in turn makes me think that if HAL is
> >> remembering a device that is no longer there, then maybe the problem is
> >> in the HAL logic.   Are the supporters of that code on this mailing
> list
> >> or is that a kernel topic?
> >
> > Drew, I agree.  I haven't had time to try reproducing this yet, but this
> > feels like a regression in the HAL behaviour.  I know that multiple
> > libusb / HAL syncing worked just fine for me.  Either it is device
> > specific or is a regression outside of gnome-pilot.
> >
> I agree on this too. In my opinion hal should not keep disconnected
> devices, or at least notify again if it's reconnected
> >
> > Tom, what HAL version do you have installed?  It would be great if we
> > could narrow this down to a HAL change, but I'll fire off a message to
> > the hal list once I know what version this behaviour has been seen in.
> >
> hal: 0.5.9.1
> hal-info: 0.20070831
> kernel: 2.6.22-ARCH
> udev: 115
>
> I'm using archlinux, which basically means I almost always have the
> latest packages.
> If you need any more versions of a certain package, you can find it
> here: http://archlinux.org/packages/search/?sort=-last_update
>
> Regards,
> Tom
> _______________________________________________
> gnome-pilot-list mailing list
> [email protected]
> http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
>

_______________________________________________
gnome-pilot-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnome-pilot-list