public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: sl@whiskey.fireplug.net (Stuart Lynne)
To: mtd@infradead.org
Subject: Re: Re[2]: Has MTD production quality support for DOC2000?
Date: 14 Aug 2000 01:02:18 -0700	[thread overview]
Message-ID: <8n892a$10c$1@whiskey.fireplug.net> (raw)
In-Reply-To: 200008102356.QAA02347@devel.ftel.com

In article <200008102356.QAA02347@devel.ftel.com>,
Mike Kilburn <mkilburn@ftel.net> wrote:
>David Woodhouse <dwmw2@redhat.com> wrote:
>> 
>> Linking the M-Systems drivers into your kernel will place _you_ in violation
>> of the GPL and you may be sued, so why not help out with the MTD drivers?
>> 
>
>Also, last I checked, the M-Systems driver disables interrupts for quite
>a long time while writing to the device. This makes it unusable in
>a real-time embedded system. Switch to a SanDisk if you can.

The new driver addresses this issue. It is not actually the driver that 
disables interrupts, the block layer does it before calling the device
request function. And in some cases the driver can take some time writing
due to erasing. The new driver will do a schedule_timeout() instead of
busy waiting.

-- 
                                            __O 
Fireplug - a Lineo company                _-\<,_ 
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
Stuart Lynne <sl@fireplug.net>       www.fireplug.net        604-461-7532


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

  parent reply	other threads:[~2000-08-14  8:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-10 12:33 Has MTD production quality support for DOC2000? Sigurd Urdahl
2000-08-10 12:44 ` David Woodhouse
2000-08-10 23:56   ` Re[2]: " Mike Kilburn
2000-08-11  1:17     ` Jon Burford
2000-08-14  8:02     ` Stuart Lynne [this message]
2000-08-11  8:16   ` Sigurd Urdahl
2000-08-11  9:09     ` Ollie Lho
2000-08-11  9:53     ` Rogelio M. Serrano Jr.
2000-08-14  8:00     ` Stuart Lynne

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='8n892a$10c$1@whiskey.fireplug.net' \
    --to=sl@whiskey.fireplug.net \
    --cc=mtd@infradead.org \
    --cc=sl@fireplug.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