9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] my ts7200 port
Date: Mon,  6 Jul 2009 23:50:14 -0400	[thread overview]
Message-ID: <df27085b5944a6a2d8d792a3b7e4ceea@quanstro.net> (raw)
In-Reply-To: <3aaafc130907061639m3e1ff6d3m38b258fb8f79d73a@mail.gmail.com>

On Mon Jul  6 19:41:36 EDT 2009, jrm8005@gmail.com wrote:
> On Mon, Jul 6, 2009 at 7:37 PM, ron minnich<rminnich@gmail.com> wrote:
> > I just ported the linux driver
>
> I'm interested in how hard this is, and how it might be made easier.

that depends.  i've found that porting a driver or working backwards
from an example is often harder than just writing a new driver.
this is because the hard part is understanding how the hardware works,
not in coding that knowledge up.  and unfortunately, looking at a
linux driver hasn't been very instructive to me.

i'm sure one could create a compatability layer for certain driver types
along the lines of ndiswrapper.  but given the instability of linux
internal interfaces, this might be finished about the same time as
duke nukem forever.

- erik



  reply	other threads:[~2009-07-07  3:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 20:10 ron minnich
2009-07-06 21:49 ` Nick LaForge
2009-07-06 22:18   ` ron minnich
2009-07-06 23:01     ` Nick LaForge
2009-07-06 23:37       ` ron minnich
2009-07-06 23:39         ` J.R. Mauro
2009-07-07  3:50           ` erik quanstrom [this message]
2009-07-07 11:36             ` Ethan Grammatikidis
2009-07-07 16:04               ` Ethan Grammatikidis
2009-07-07 17:15                 ` erik quanstrom
2009-07-07  3:57         ` Dan Cross
2009-07-07  3:59           ` erik quanstrom
2009-07-07  7:06             ` Nick LaForge
2009-07-07  3:56       ` erik quanstrom

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=df27085b5944a6a2d8d792a3b7e4ceea@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).