From: David Woodhouse <dwmw2@infradead.org>
To: Paonia Ezrine <paonia@home.welcomehome.org>
Cc: mtd@infradead.org
Subject: Re: read only
Date: Thu, 04 May 2000 09:00:56 +0100 [thread overview]
Message-ID: <24367.957427256@devel2.axiom.internal> (raw)
In-Reply-To: <200005032221.SAA10825@home.welcomehome.org>
paonia@home.welcomehome.org said:
> I am looking to use the DOC or similar with lrp. Is there a way to set
> the device to read only mode so that no one can hack with it. I dont
> mean a software setting but a hardware one. Also which DOC or similar
> would people project for this application. Porlby need 2-20 megs.
Not in hardware AFAIK - at least not simply by cutting control lines -
you'd have to have some intelligence in between your system bus and the
DiskOnChip. (logic: when the host writes to location 0x1004 in the device,
you ensure that bit 3 (WP) is _always_ set - mask it in if the host didn't
set it.)
However, it's quite feasible to cut out the write capability in the device
driver, so that an attacker would have to load his own driver for it if he
wanted to write to it. That would probably be enough for your purposes.
I've been intending to do that for a while now anyway - as it would mean I
could mark the write support as experimental.
In fact, read-only support is all I'd really want people to use the MTD
DiskOnChip driver for right now.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-05-04 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-03 22:21 read only Paonia Ezrine
2000-05-04 8:00 ` David Woodhouse [this message]
2000-05-04 17:41 ` Paonia Ezrine
2000-05-05 8:22 ` David Woodhouse
2000-05-05 8:24 ` Trevor Woolven
2000-05-05 9:20 ` David Woodhouse
2000-05-07 10:38 ` Dvir Oren
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=24367.957427256@devel2.axiom.internal \
--to=dwmw2@infradead.org \
--cc=mtd@infradead.org \
--cc=paonia@home.welcomehome.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