public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brendan J Simon <brendan.simon@ctam.com.au>
To: mtd@infradead.org
Subject: Re: Integrating 2000 and Millenium drivers
Date: Tue, 15 Aug 2000 10:37:34 +1000	[thread overview]
Message-ID: <399890CE.A0F606F0@ctam.com.au> (raw)
In-Reply-To: 6011381691@mamao.cetuc.puc-rio.br

I don't know the code very well, but I would push for code reuse where ever
possibl
 Maybe there should be three file ???  One that has the common/shared code,
one for Doc2000 specific code and one for DocMil specific code ???

Brendan Simon.


Miguel Freitas wrote:

>     Hi,
>     I'm fixing some little things on DOC2000 driver, and I'm wondering
> if we could integrate 2k and Millenium drivers in a single file. There
> is so many common code in these two drivers that I guess we could
> do it like m-sys do: a single driver with a flag to enable all pipeline
> stuff from millenium and registers. A single variable pointing to the
> IO register would also be nice.
>     I agree that from a first version perspective it's better to develop
> two drivers. We can work in all 2k or Mil little tricks without breaking
> the other. But maybe we are reaching a stable low level routines
> where the merge could be done.
>     I don't have the millenium hardware, so I would probably break
> everything for millenium users if I make this merge. Is there
> someone with knowledge of DoC Mil (and spare time!) to help me
> with it?
>
>     BTW, I've just begin hacking DoC last month, so forgive me if I'm
> missing some good reason why these drivers can't be merged...
>
> Regards,
>
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-08-15  0:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-14 22:38 Integrating 2000 and Millenium drivers Miguel Freitas
2000-08-15  0:37 ` Brendan J Simon [this message]
2000-08-15  7:29 ` David Woodhouse

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=399890CE.A0F606F0@ctam.com.au \
    --to=brendan.simon@ctam.com.au \
    --cc=mtd@infradead.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