From: David Brownell <david-b@pacbell.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: dbrownell@users.sourceforge.net,
kernel list <linux-kernel@vger.kernel.org>,
Rusty trivial patch monkey Russell <trivial@rustcorp.com.au>
Subject: Re: Support sharp zaurus C-750
Date: Mon, 21 Jul 2003 13:18:26 -0700 [thread overview]
Message-ID: <3F1C4A92.2000305@pacbell.net> (raw)
In-Reply-To: <20030720230530.GA2075@elf.ucw.cz>
Pavel Machek wrote:
> Hi!
>
> This adds support for another handheld from sharp to 2.6.0-test1,
> please apply:
I'll tweak it a bit, so that it's identifed as a C-7x0 not as
an A-300, and merge it through Greg into 2.6 and 2.4. Thanks
for the patch!
Here's where I wish Sharp took a more enlightened approach to
their firmware: they _could_ just modify the firmware revision
number and descriptive strings. They're gratuitously requiring
a new host-side driver for each new product variant, which is
just a PITA. Maybe by the time these get distributed in the US,
that can be resolved.
You wouldn't happen to have the C-760 product ID too, would you?
(That's got more flash and battery power.)
- Dave
next prev parent reply other threads:[~2003-07-21 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 23:05 Support sharp zaurus C-750 Pavel Machek
2003-07-21 20:18 ` David Brownell [this message]
2003-07-30 19:59 ` Greg KH
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=3F1C4A92.2000305@pacbell.net \
--to=david-b@pacbell.net \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=trivial@rustcorp.com.au \
/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