Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: ralf@mailhost.uni-koblenz.de
Cc: Oliver Frommel <oliver@aec.at>, Mike Shaver <shaver@netscape.com>,
	Alex deVries <adevries@engsoc.carleton.ca>,
	SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: root-be-0.03.tar.gz
Date: Sun, 25 Jan 1998 12:47:31 +0100	[thread overview]
Message-ID: <19980125124731.10567@alpha.franken.de> (raw)
In-Reply-To: <19980124141627.19289@uni-koblenz.de>; from ralf@mailhost.uni-koblenz.de on Sat, Jan 24, 1998 at 02:16:27PM +0100

> > is there a way to do a raw disk access via ARC firmware ? Mabye we could
> > use some bits from SILO (Sparc Linux Loader) and get ext2fs access this
> > way. 
> 
> That´s one way.  Another would be to do it like the Alpha Milo.

which would be IMHO a real overkill (Alpha Milo is nearly a complete
Linux kernel with some special stuff for bringing up the hardware). It 
makes sense for Alphas as there are ARC only machines out, and the 
ARC PAL code isn't suited for Linux. So you have to replace the PAL code and
after that the ARC firmware isn't able to do anything, so Alpha Milo has 
to boot the kernel itself. To this it needs to access the hardware and
as the Linux drivers has already been available, why not use them ?
Alpha Milo can also be used as the real firmware on some Alpha boards 
(I've flashed Alpha Milo, so my Alpha doesn't see any ARC stuff).
For Mips Milo we don't need to change PAL code change or other strange
stuff and with raw partition access we can do all what we want.

> Raw access should work by accessing something like
> scsi(0)disk(0)rdisk(1)partition(0) or so.  Milo should actually already
> provide all the framework required for easy implementation of ext2fs
> access.

good, I will to some tests:-)

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

  reply	other threads:[~1998-01-25 12:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-21 18:59 root-be-0.03.tar.gz Alex deVries
1998-01-21 19:38 ` root-be-0.03.tar.gz Mike Shaver
1998-01-21 20:26   ` root-be-0.03.tar.gz Alan Cox
1998-01-21 20:26     ` root-be-0.03.tar.gz Alan Cox
1998-01-22  6:04   ` root-be-0.03.tar.gz Alex deVries
1998-01-22  6:11     ` root-be-0.03.tar.gz Mike Shaver
1998-01-22 12:04       ` root-be-0.03.tar.gz Oliver Frommel
1998-01-22 18:18         ` root-be-0.03.tar.gz William J. Earl
1998-01-23  3:57         ` root-be-0.03.tar.gz ralf
1998-01-23 17:43           ` root-be-0.03.tar.gz William J. Earl
1998-01-23 22:24           ` root-be-0.03.tar.gz Thomas Bogendoerfer
1998-01-24 13:16             ` root-be-0.03.tar.gz ralf
1998-01-25 11:47               ` Thomas Bogendoerfer [this message]
1998-01-22 10:29     ` root-be-0.03.tar.gz Alan Cox
1998-01-22 10:29       ` root-be-0.03.tar.gz Alan Cox
1998-01-22 20:39     ` root-be-0.03.tar.gz Alistair Lambie
1998-01-22 21:37       ` root-be-0.03.tar.gz William J. Earl
1998-01-22 22:18         ` root-be-0.03.tar.gz Alistair Lambie

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=19980125124731.10567@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=adevries@engsoc.carleton.ca \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=oliver@aec.at \
    --cc=ralf@mailhost.uni-koblenz.de \
    --cc=shaver@netscape.com \
    /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