public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
* mtd on linux
@ 2001-04-13  5:13 Manatee
  2001-04-13 22:48 ` R: " Alessandro Staltari
  2001-04-17 14:52 ` David Woodhouse
  0 siblings, 2 replies; 8+ messages in thread
From: Manatee @ 2001-04-13  5:13 UTC (permalink / raw)
  To: mtd


Hi,

I compiled the 2.4.1 kernel for Linux which has support for this device.
Then I put the card in the PCI slot and rebooted. My harddrive was not
recognized.

What I want to do is just boot up as normal and then mount the card and
take a look at what is on it. Just curious. Could someone tell me how to
install the card so it does not interfere with normal booting? And once I
boot up how, specifically, can I take a look at what is on the 'disk on
chip'? Thank you.

Manatee



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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* R: mtd on linux
  2001-04-13  5:13 mtd on linux Manatee
@ 2001-04-13 22:48 ` Alessandro Staltari
  2001-04-14  6:20   ` Manatee
  2001-04-17 14:52 ` David Woodhouse
  1 sibling, 1 reply; 8+ messages in thread
From: Alessandro Staltari @ 2001-04-13 22:48 UTC (permalink / raw)
  To: Manatee, mtd

> I compiled the 2.4.1 kernel for Linux which has support for this device.
> Then I put the card in the PCI slot and rebooted. My harddrive was not
> recognized.
>

It seems original DOC firmware interfere with lilo. M-sys provides an
alternate DOC firmware to allow linux boot from hard drive but I prefer
booting from a floppy by copying the kernel image to it (cp zImage
/dev/fd0).

I hope this helps

Alessandro Staltari




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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: R: mtd on linux
  2001-04-13 22:48 ` R: " Alessandro Staltari
@ 2001-04-14  6:20   ` Manatee
  2001-04-14  9:09     ` R: " Alessandro Staltari
  0 siblings, 1 reply; 8+ messages in thread
From: Manatee @ 2001-04-14  6:20 UTC (permalink / raw)
  To: Alessandro Staltari; +Cc: mtd


On Sat, 14 Apr 2001, Alessandro Staltari wrote:

> It seems original DOC firmware interfere with lilo. M-sys provides an
> alternate DOC firmware to allow linux boot from hard drive but I prefer
> booting from a floppy by copying the kernel image to it (cp zImage
> /dev/fd0).
>
> I hope this helps

Yes, thank you.

So you are saying that all I have to do is boot my Linux kernel from a
floppy and then I can talk to my disk on chip?

So once I have booted up, using a floppy, then how do I access the disk
on chip? Do I mount it, then cd to it, and then do a 'ls' to see what is
there, etc.?

Manatee



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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* R: R: mtd on linux
  2001-04-14  6:20   ` Manatee
@ 2001-04-14  9:09     ` Alessandro Staltari
  0 siblings, 0 replies; 8+ messages in thread
From: Alessandro Staltari @ 2001-04-14  9:09 UTC (permalink / raw)
  To: Manatee; +Cc: mtd

> So once I have booted up, using a floppy, then how do I access the disk
> on chip? Do I mount it, then cd to it, and then do a 'ls' to see what is
> there, etc.?

Now I'm not using MTD but there is people that is using that, so I belive
this is really possible.

Regards

Alessandro.



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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: mtd on linux
  2001-04-13  5:13 mtd on linux Manatee
  2001-04-13 22:48 ` R: " Alessandro Staltari
@ 2001-04-17 14:52 ` David Woodhouse
  2001-04-17 16:20   ` Manatee
  1 sibling, 1 reply; 8+ messages in thread
From: David Woodhouse @ 2001-04-17 14:52 UTC (permalink / raw)
  To: Manatee; +Cc: mtd


manatee@pacifier.com said:
>  I compiled the 2.4.1 kernel for Linux which has support for this device.

Which device?

> Then I put the card in the PCI slot and rebooted. 

Which card?

> My harddrive was not recognized. 

I know nothing about harddrives. 


manatee@pacifier.com said:
> What I want to do is just boot up as normal and then mount the card
> and take a look at what is on it. Just curious. Could someone tell me
> how to install the card so it does not interfere with normal booting?
> And once I boot up how, specifically, can I take a look at what is on
> the 'disk on chip'? Thank you. 

Do you have a DiskOnChip on an evaluation board? The way I prevent it from 
interfering with normal booting is to remove the jumper which controls the 
memory window during booting, and replace it after the grub or lilo prompt 
has appeared. If you _never_ want to boot from it, you can just destroy the 
firmware on it. M-Systems provide an 'fff.exb' or similarly named firmware 
file for this purpose.

If you get Linux to boot, with the DOC2000 and NFTL config options 
turned on (or if you load the modules), then you ought to be able to access 
the device as /dev/nftla (block 93,0) and /dev/nftla1 (block 93,1). 

--
dwmw2




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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: mtd on linux
  2001-04-17 14:52 ` David Woodhouse
@ 2001-04-17 16:20   ` Manatee
  2001-04-17 16:23     ` David Woodhouse
  0 siblings, 1 reply; 8+ messages in thread
From: Manatee @ 2001-04-17 16:20 UTC (permalink / raw)
  To: David Woodhouse; +Cc: mtd


On Tue, 17 Apr 2001, David Woodhouse wrote:

> Which device?

It is a Disk On Chip and it fits into a PCI slot.

> Do you have a DiskOnChip on an evaluation board? The way I prevent it from
> interfering with normal booting is to remove the jumper which controls the
> memory window during booting, and replace it after the grub or lilo prompt
> has appeared. If you _never_ want to boot from it, you can just destroy the
> firmware on it. M-Systems provide an 'fff.exb' or similarly named firmware
> file for this purpose.

I see where jumpers would go but there are no jumpers on the card.


> If you get Linux to boot, with the DOC2000 and NFTL config options
> turned on (or if you load the modules), then you ought to be able to access
> the device as /dev/nftla (block 93,0) and /dev/nftla1 (block 93,1).

Ah, so if I can get the machine to boot -- with the card in place -- then
I can access the card.

Manatee



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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: mtd on linux
  2001-04-17 16:20   ` Manatee
@ 2001-04-17 16:23     ` David Woodhouse
  2001-04-17 17:35       ` Bari Ari
  0 siblings, 1 reply; 8+ messages in thread
From: David Woodhouse @ 2001-04-17 16:23 UTC (permalink / raw)
  To: Manatee; +Cc: mtd


manatee@pacifier.com said:
>  It is a Disk On Chip and it fits into a PCI slot. 

OK. I'd heard of those but haven't actually met one yet.

>  I see where jumpers would go but there are no jumpers on the card.

I was thinking of the ISA eval board.

>  Ah, so if I can get the machine to boot -- with the card in place --
> then I can access the card. 

Probably. It depends just how the PCI eval board is set up. Isn't there a 
key sequence you can use during booting to prevent the DiskOnChip BIOS from 
loading itself? Or use the DFORMAT program provided to load the null 
firmware. 

--
dwmw2




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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: mtd on linux
  2001-04-17 16:23     ` David Woodhouse
@ 2001-04-17 17:35       ` Bari Ari
  0 siblings, 0 replies; 8+ messages in thread
From: Bari Ari @ 2001-04-17 17:35 UTC (permalink / raw)
  To: David Woodhouse; +Cc: Manatee, mtd

David Woodhouse wrote:

> manatee@pacifier.com said:
> 
>>  It is a Disk On Chip and it fits into a PCI slot. 
> 
> 
> OK. I'd heard of those but haven't actually met one yet.
> 
>>  I see where jumpers would go but there are no jumpers on the card.
> 
> 
> I was thinking of the ISA eval board.
> 
>>  Ah, so if I can get the machine to boot -- with the card in place --
>> then I can access the card. 
> 
> 
> Probably. It depends just how the PCI eval board is set up. Isn't there a 
> key sequence you can use during booting to prevent the DiskOnChip BIOS from 
> loading itself? Or use the DFORMAT program provided to load the null 
> firmware. 

Check the M-Sys DOC-DIP-EVB-PCI manual. It says the "DiskOnChip base 
address - 0xD000 (Fixed)"

What happens when you boot? Do you get a conflict error? or you just 
can't find your DOC? Did you configure your DOC for Linux?

Bari




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

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2001-04-17 17:38 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-04-13  5:13 mtd on linux Manatee
2001-04-13 22:48 ` R: " Alessandro Staltari
2001-04-14  6:20   ` Manatee
2001-04-14  9:09     ` R: " Alessandro Staltari
2001-04-17 14:52 ` David Woodhouse
2001-04-17 16:20   ` Manatee
2001-04-17 16:23     ` David Woodhouse
2001-04-17 17:35       ` Bari Ari

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox