From: Greg KH <greg@kroah.com>
To: Paco Ros <switch@tiscali.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: visor module and Palm Zire 71 problem.
Date: Thu, 18 Sep 2003 11:29:03 -0700 [thread overview]
Message-ID: <20030918182903.GC1846@kroah.com> (raw)
In-Reply-To: <200309132008.17716.switch@tiscali.es>
On Sat, Sep 13, 2003 at 08:08:17PM +0200, Paco Ros wrote:
> Hi!
>
> I bought one of these nice Palm handhelds with integrated camera.
> I was running 2.4.20 kernel at that time and I modified the following files:
> - drivers/usb/serial/visor.h
> added #define PALM_ZIRE71_ID 0x0060
>
> - drivers/usb/serial/visor.c
> added id_table and id_table_combined definitions.
>
> You have both modified from 2.4.20 files here:
> http://bulmalug.net/~pacoros/articulos/visor.c
> http://bulmalug.net/~pacoros/articulos/visor.h
This device has been supported for a while now, just upgrade your kernel
please.
> They were working fine with pilot-link software.
>
> Some weeks ago I compiled a 2.4.22-ac1 kernel and I saw that a new version of visor was released.
> I haven't been able to make my Zire 71 work with this kernel version.
>
> The trick of adding PALM_ZIRE71_ID definition does not work anymore
> and I get a Oops! when the module tries to be removed. Here is the
> log:
This device should just work with this kernel, the driver does not need
to be modified.
> I've been googling and looking for visor project and seems to be
> completely integrated in kernel tree and no news or movement is
> appreciated at usbvisor web site.
The usbvisor web site is dead as the maintainer for it has disappeared.
The kernel driver is kept quite up to date.
thanks,
greg k-h
prev parent reply other threads:[~2003-09-18 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 18:08 visor module and Palm Zire 71 problem Paco Ros
2003-09-18 18:29 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030918182903.GC1846@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=switch@tiscali.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox