From: David Woodhouse <dwmw2@infradead.org>
To: Dvir Oren <dviro@lucidvon.com>
Cc: MTD <mtd@infradead.org>
Subject: Re: Hardware RO & delays [DOC2000]
Date: Fri, 07 Jan 2000 09:15:40 +0000 [thread overview]
Message-ID: <E126VUj-0006ne-00@devel2.axiom.internal> (raw)
In-Reply-To: <E126NIB-0005it-00@infradead.org>
dviro@lucidvon.com said:
> 1. Is there a way to tell the flash (DoC2000) to mark a certain part
> of it as read only? I know I can mount a certain partition as read
> only, but can I protect it at a lower level?
Not per partition, but per NFTL. Yes - if you modify nftl.c to register the
blockdevice as readonly, then refuse to process any writes to that device,
you'll be fine.
You can have more than one NFTL 'drive' on each DiskOnChip, arccording to my
reading of the specifications - although I'm not sure if the firmware will see
both of them. You might need to make sure the boot drive is the first one on
the DiskOnChip, so that the BIOS sees it.
> 2. Does the driver block the system? I'm experience delays in
> sending udp packets over ethernet for periods of 50-300 miliseconds.
> I have a function that is supposed to send every several miliseconds
> a packets, and when going over the logs, I once in a while see a
> packet that is delayed for several tens of miliseconds, which is not
> acceptable by me.
Yes, it does all its flash access, even waiting for erases to finish, with
interrupts disabled.
> Any ideas?
Yes. I know exactly how I'm going to thread it, and lock the device / each
chip etc. against multiple accesses. I just haven't done it yet.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-01-07 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-04 21:45 Hardware RO & delays [DOC2000] Dvir Oren
2000-01-07 2:01 ` Brendan J Simon
2000-01-07 15:55 ` Dvir Oren
2000-01-07 9:15 ` David Woodhouse [this message]
2000-01-07 15:55 ` Dvir Oren
2000-01-07 16:10 ` David Woodhouse
2000-01-14 1:37 ` i hope to write open source's firmware jyllyj
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=E126VUj-0006ne-00@devel2.axiom.internal \
--to=dwmw2@infradead.org \
--cc=dviro@lucidvon.com \
--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