Re: Shit Happens...

Tyler Dauwalder <tyler-cyCl/[email protected]>
Newsgroups gmane.os.openbeos.storage
Message-ID <[email protected]>
> > > and 3) I somehow suspect the
> > > disk_scanner module code not to be endianess aware (at least the
> > > partition module isn't).
> >
> > Argh. Mine isn't either. It didn't occur to me at the time, I'm sad=20
> > to
> > say (though it'd be fairly easy to fix).
>=20
> Earlier or later we should definitely fix it. But I suspect, there is
> little chance, that there will be any alternative processor to x86
> compatibles till R1. So it's not critical for the time being.

I'll just go ahead and fix mine when I get the chance.

> > > To cut a long story short, I will either need to get my desktop
> > > machine
> > > running again or get a new laptop before I will be able to=20
> > > continue to
> > > contribute. Unfortunately my financial situation isn't so great,=20
> > > that
> > > I
> > > wouldn't need to think about it.
> >
> > Well, I hope you manage to get something worked out, but certainly
> > one's financial priorities must come first. If there's anything I=20
> > can
> > do to help get things working, let me know.
>=20
> Thanks. I think, I made up my mind, and I will buy a new machine=20
> rather
> soon. I'm actually a bit surprised how much the prices for laptops=20
> have
> dropped. One can get quite a hell of a machine for like 1500 bucks.=20
> My old
> one including a network adapter and a modem was almost twice as=20
> expensive.
> So, I'll investigate some days and scratch the money together in=20
> about a
> week or two at the latest.

Good deal. Have fun. :-)

> > > but e.g. soundwise I've no idea.
> >
> > Mine doesn't work, so I'll look it up tomorrow and let you know=20
> > (it's
> > terribly late at the moment...). My wireless card is unsupported as
> > well.
>=20
> My old sound card, a ESS Maestro 2e, didn't work either. There was=20
> even a
> driver, but it crashed and Daniel Berlin never cared to answer my=20
> requests
> for the source code. :-(
> So at least it wouldn't be worse, if the sound card wasn't supported,=20
> but
> I hope for an improvement, of course. :-P

My sound is a Crystal 4205, my built-in ethernet is a 3com 3c920=20
(supposedly 3c905c-tx compatible), and my wireless ethernet card is an=20
Orinoco Gold, none of which are supported (neither R5 nor BONE).=20

On 2003-03-02 at 13:17:28 [-0800], Axel D=F6rfler wrote:
> > > > and 3) I somehow suspect the
> > > > disk=3D5Fscanner module code not to be endianess aware (at least=20
> > > > the
> > > > partition module isn't).
> > > Argh. Mine isn't either. It didn't occur to me at the time, I'm=20
> > > sad
> > > to
> > > say (though it'd be fairly easy to fix).
> > Earlier or later we should definitely fix it. But I suspect, there=20
> > is
> > little chance, that there will be any alternative processor to x86
> > compatibles till R1. So it's not critical for the time being.
>=20
> You might actually be wrong here: it looks like I get a PPC board (G3/
> 600 MHz - fanless!) for free to port OpenBeOS over (which I'd happily
> do).
> And then, I will have to make sure that all sub-systems are endian-
> aware over time. But that's no big deal for the kernel in general
> anyway. That will also mean that I will probably have to write
> partition scanners for Amiga/Apple partitioning scheme (since IIRC
> that's what the firmware supports).
> Since it's open firmware based, it will also mean that we will get=20
> some
> drivers (like IDE/SCSI/and probably USB) for free (we will only have=20
> to
> write a small wrapper which enables them). So when we have our
> config=3D5Fmanager/devfs architecture in place, it's likely to be the=20
> first
> system to boot OpenBeOS from a hard drive and BFS volume (which will
> have to be endian aware, too).

Would that mean I could run it on my iMac, too, then? That would be=20
great (I still can't get OS X to install on the damn thing...).

-Tyler
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.