From: David Woodhouse <dwmw2@infradead.org>
To: David Given <dg@tao-group.com>
Cc: mtd@infradead.org
Subject: Re: sbc-mediagx
Date: Wed, 13 Sep 2000 17:43:22 +0100 [thread overview]
Message-ID: <32401.968863402@passion.cygnus.co.uk> (raw)
In-Reply-To: <E13ZFNG-00020Z-00@pearl.tao.co.uk>
dg@tao-group.com said:
> * MTD only works with kernels compiled with*out* MODVERSIONS. This is
> because the dynamic loading code in map.h doesn't know about the
> mangled symbols used with this option turned on.
Easy to fix - just that nobody's bothered yet. Patches accepted if you care
enough to produce one.
dg@tao-group.com said:
> * The device claims to see only 8MB of my flash medium.
Odd. Please send the kernel's output while it's probing. How big _is_ the
flash?
dg@tao-group.com said:
> * The device sees three partitions on the disk. DOS sees one. I
> suspect that they use different concepts of partitions.
Yes. In hindsight, we probably shouldn't call them 'partitions'.
dg@tao-group.com said:
> * MTD doesn't work with devfs, so you have to create device nodes
> manually --- /dev/mtd is at c,90,0..2 and /dev/mtdblock is at
> b,31,0..2, right?
See #1. Patches accepted if you care :)
dg@tao-group.com said:
> Would anyone like to explain to me what's going on, if anyone knows?
> I *really* don't want to go back to using flashfx.o. I don't want to
> experiment as I could easily render my board unbootable. Which would
> be a shame.
Please could you bzip2 and send to me the contents of /dev/mtd[012]. I'm
not 100% sure what translation layer is used by flashfx, but it might be
something I recognise.
dg@tao-group.com said:
> BTW, anyone know how frequently the kernel syncs with the CVS tree?
Rarely at the moment. I sync to Linus' kernel frequently, but I'm not
intending to send him anything more for 2.4. Once the 2.5 series starts,
I'll be keeping it reasonably up-to-date.
AnonCVS access is available. I recommend you use that.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-09-13 16:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-13 16:27 sbc-mediagx David Given
2000-09-13 16:43 ` David Woodhouse [this message]
2000-09-13 17:08 ` sbc-mediagx David Given
2000-09-13 17:37 ` sbc-mediagx David Given
2000-09-13 18:10 ` sbc-mediagx David Given
2000-09-14 9:04 ` sbc-mediagx David Woodhouse
2000-09-14 10:03 ` sbc-mediagx David Given
2000-09-14 11:15 ` sbc-mediagx David Given
2000-09-14 9:35 ` sbc-mediagx David Vrabel
2000-10-27 0:08 ` kernel syncs Alice Hennessy
2000-10-27 9:00 ` David Woodhouse
[not found] <39C08AB9.1DF0409B@arcom.co.uk>
2000-09-14 10:59 ` sbc-mediagx David Given
2000-09-14 11:45 ` sbc-mediagx Kira Brown
[not found] <NEBBLLDBMLGONJHPHHEKGEMLCHAA.ajlennon@arcom.co.uk>
2000-09-14 12:54 ` sbc-mediagx David Woodhouse
2000-09-14 13:12 ` sbc-mediagx Alex J Lennon
2000-09-14 13:20 ` sbc-mediagx David Woodhouse
2000-09-15 20:23 ` sbc-mediagx Scott Anderson
-- strict thread matches above, loose matches on Subject: below --
2000-09-29 12:55 SBC-MediaGX Michiel Ronsse
2000-09-29 15:15 ` SBC-MediaGX David Given
2000-09-29 17:20 ` SBC-MediaGX Michiel Ronsse
2000-09-29 17:47 re[2]: SBC-MediaGX Tony Questad
2000-09-30 11:19 ` SBC-MediaGX Alex J Lennon
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=32401.968863402@passion.cygnus.co.uk \
--to=dwmw2@infradead.org \
--cc=dg@tao-group.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