From: Dan Malek <dan@embeddededge.com>
To: Ulrich Eckhardt <eckhardt@satorlaser.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Au1100 FB driver uplift for 2.6
Date: Tue, 5 Apr 2005 12:49:41 -0400 [thread overview]
Message-ID: <de11cd376cdc88e9c292ae7e204e2de9@embeddededge.com> (raw)
In-Reply-To: <200504041717.29098.eckhardt@satorlaser.com>
On Apr 4, 2005, at 11:17 AM, Ulrich Eckhardt wrote:
> Am I on the wrong way or should I just reimplement it and send a patch?
If you an test it, do it and send a patch.
> [2] Based on DB1100. Are there any pointers on how to port to a new
> board,
> btw?
One of the discussion items is always how to keep a "generic"
driver and still provide unique setup/control for different types of
boards. I guess if we can discuss other board ports, it will be
more clear how to do this.
Thanks.
-- Dan
next prev parent reply other threads:[~2005-04-05 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 15:17 Au1100 FB driver uplift for 2.6 Ulrich Eckhardt
2005-04-05 16:49 ` Dan Malek [this message]
2005-04-06 7:13 ` Porting to new board [was: Re: Au1100 FB driver uplift for 2.6] Ulrich Eckhardt
2005-04-06 9:31 ` Au1100 FB driver uplift for 2.6 Ulrich Eckhardt
2005-04-06 14:34 ` Ulrich Eckhardt
2005-04-06 15:53 ` Pete Popov
2005-04-06 17:58 ` Ulrich Eckhardt
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=de11cd376cdc88e9c292ae7e204e2de9@embeddededge.com \
--to=dan@embeddededge.com \
--cc=eckhardt@satorlaser.com \
--cc=linux-mips@linux-mips.org \
/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