* nftl
@ 2001-12-04 22:07 Mike Ruthven
0 siblings, 0 replies; 5+ messages in thread
From: Mike Ruthven @ 2001-12-04 22:07 UTC (permalink / raw)
To: linux-mtd
2 quick problems:
nftl_format gives error
Erase size not 8Kb - I'm confused
loading nftl module gives error
Sorry, we don't support UnitSizeFactor of != 1 yet.
Could not find valid boot record
Could not mount NFTL device
Somehow these seem related to me. Any suggestions?
Mike Ruthven, R&D Specialist
Creonova Systems Inc.
mike@creonova.com (519)767-0067
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: nftl
@ 2001-12-05 15:25 ilatypov
2001-12-05 15:41 ` nftl David Woodhouse
0 siblings, 1 reply; 5+ messages in thread
From: ilatypov @ 2001-12-05 15:25 UTC (permalink / raw)
To: Mike Ruthven; +Cc: linux-mtd
Mike,
On Tue, 4 Dec 2001, Mike Ruthven wrote:
> nftl_format gives error
> Erase size not 8Kb - I'm confused
Comment out the conditional statement. David Woodhouse explained that
the only reason for this check is that NFTL formatting with the other
erase block sizes is not tested.
> loading nftl module gives error
> Sorry, we don't support UnitSizeFactor of != 1 yet.
> Could not find valid boot record
> Could not mount NFTL device
I encountered the same with an M-Sys-pre-formatted DOC chip. It seems
that the existing MTD code will work only after re-formatting the chip
with the nftl_format. Correct me if I am wrong.
Ilguiz
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: nftl
2001-12-05 15:25 nftl ilatypov
@ 2001-12-05 15:41 ` David Woodhouse
2001-12-05 16:18 ` nftl Mike Ruthven
0 siblings, 1 reply; 5+ messages in thread
From: David Woodhouse @ 2001-12-05 15:41 UTC (permalink / raw)
To: ilatypov; +Cc: Mike Ruthven, linux-mtd
ilatypov@infradead.org said:
> I encountered the same with an M-Sys-pre-formatted DOC chip. It
> seems that the existing MTD code will work only after re-formatting
> the chip with the nftl_format. Correct me if I am wrong.
Shouldn't take much to make that format work with our NFTL code. Again,
it's disabled mostly because it's not tested.
--
dwmw2
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: nftl
2001-12-05 15:41 ` nftl David Woodhouse
@ 2001-12-05 16:18 ` Mike Ruthven
2001-12-05 16:20 ` nftl David Woodhouse
0 siblings, 1 reply; 5+ messages in thread
From: Mike Ruthven @ 2001-12-05 16:18 UTC (permalink / raw)
To: David Woodhouse, ilatypov; +Cc: linux-mtd
> -----Original Message-----
> From: David Woodhouse [mailto:dwmw2@redhat.com]On Behalf Of David
> Woodhouse
> Sent: December 5, 2001 10:42 AM
> To: ilatypov@infradead.org
> Cc: Mike Ruthven; linux-mtd@lists.infradead.org
> Subject: Re: nftl
>
>
>
> ilatypov@infradead.org said:
> > I encountered the same with an M-Sys-pre-formatted DOC chip. It
> > seems that the existing MTD code will work only after re-formatting
> > the chip with the nftl_format. Correct me if I am wrong.
>
> Shouldn't take much to make that format work with our NFTL code. Again,
> it's disabled mostly because it's not tested.
>
> --
> dwmw2
>
>
That's it. Thanks.
Not that one case is a test, but I was able to nftl_format my DOC with erase
size 0x4000.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: nftl
2001-12-05 16:18 ` nftl Mike Ruthven
@ 2001-12-05 16:20 ` David Woodhouse
0 siblings, 0 replies; 5+ messages in thread
From: David Woodhouse @ 2001-12-05 16:20 UTC (permalink / raw)
To: Mike Ruthven; +Cc: ilatypov, linux-mtd
mike@creonova.com said:
> Not that one case is a test, but I was able to nftl_format my DOC with
> erase size 0x4000.
Yeah - but did it _work_ afterwards? :)
--
dwmw2
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2001-12-05 16:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-12-05 15:25 nftl ilatypov
2001-12-05 15:41 ` nftl David Woodhouse
2001-12-05 16:18 ` nftl Mike Ruthven
2001-12-05 16:20 ` nftl David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-12-04 22:07 nftl Mike Ruthven
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox