> > Bummer, I don't have it anymore. And my 2.6.19-rc2 tree doesn't compile yet
> > for Atari.
> >
> > I'll see whether I can get it `working'[*] again...
> >
> > [*] "If it compiles, it is good, if it boots up it is perfect."
> > -- Linus Tor
On Mon, 16 Oct 2006, Geert Uytterhoeven wrote:
> On Mon, 16 Oct 2006, Michael Schmitz wrote:
> > Geert: can you send me the kernel binary that only did a black screen for
> > you? I'd like to test it on the hardware itself...
>
> Bummer, I don't have it anymore. And my 2.6.19-rc2 tree doesn't comp
On Mon, 16 Oct 2006, Michael Schmitz wrote:
> Geert: can you send me the kernel binary that only did a black screen for
> you? I'd like to test it on the hardware itself...
Bummer, I don't have it anymore. And my 2.6.19-rc2 tree doesn't compile yet
for Atari.
I'll see whether I can get it `workin
> > I'm not sure if it is still the case, but in the copy of the tree I
> > have handy, atari_scsi uses a local copy of NCR5380.c rather than
>
> Sure, but once upon a time, that local copy was derived from NCR5380.c and
> the business end of the logic didn't change.
>
> > the shared copy being use
Bill Allombert píše v Út 10. 10. 2006 v 20:52 +0200:
> > Do tell that to my Falcon/CT60. What did I buy the 512 MB RAM stick for?
> > :-)))
>
> True but does aranym allow more than 126Mb ?
yes. The limit (in direct addressing mode) is at about 3824 MB of
FastRAM, IIRC.
The Debian build for MMU v
On Mon, Oct 09, 2006 at 10:04:14AM +0200, Michael Schmitz wrote:
> > > the more RAM you gives to Linux the more it will like you, won't it? ;-)
> >
> > Sure, but are not we limited to about 128Mb of RAM by the plateform ?
> > This is not much by current standard.
>
> Do tell that to my Falcon/CT60
> > 2.6.17 without ADB seems pretty solid to me except for the genrtc problems
> > (I do have two nice panic logs on that issue, but these rather look like
> > the genrtc module itself is borked, as gen_rtc_ioctl+0x12a trips over a
> > NULL PC...) and the time lagging back more than one day by now.
> > I have no idea what kind of machine this happened on. If it's not Sonic or
> > IIfx, locking or interrupt reentry seems most likely. The 5380 driver of
> > old mostly relies on interrupts being masked on entry, and the big kernel
> > lock held.
>
> I hadn't looked at it that closely. However, t
> > the more RAM you gives to Linux the more it will like you, won't it? ;-)
>
> Sure, but are not we limited to about 128Mb of RAM by the plateform ?
> This is not much by current standard.
Do tell that to my Falcon/CT60. What did I buy the 512 MB RAM stick for?
:-)))
> I have still not figured
On Sun, Oct 08, 2006 at 08:25:00PM +0200, Petr Stehlik wrote:
> > plus, do i need to figure for how much ram
>
> the more RAM you gives to Linux the more it will like you, won't it? ;-)
Sure, but are not we limited to about 128Mb of RAM by the plateform ?
This is not much by current standard.
I
Brian Morris píše v So 07. 10. 2006 v 23:11 -0700:
> i did download aranym and emutos recently, i have to set it up.
you don't need emutos for running linux-m68k as ARAnyM got its own
integrated LILO.
> so, basic question, like can i try and boot aranym off this
> backup of my mac disk ? or do i
I am not sure if this is a side question/new thread or not, but...
i did download aranym and emutos recently, i have to set it up.
it was suggested as a way for me to have some help for compiling
and testing, but i have no familiarity at all with atari. (running
aranym on old world powermac with
On Sat, Oct 07, 2006 at 09:45:43AM +0200, Michael Schmitz wrote:
> I have no idea what kind of machine this happened on. If it's not Sonic or
> IIfx, locking or interrupt reentry seems most likely. The 5380 driver of
> old mostly relies on interrupts being masked on entry, and the big kernel
> lock
On Sat, 7 Oct 2006, Michael Schmitz wrote:
> > > well we haven't had much testing here on 2.6 either, making this big jump.
> >
> > It's true 2.6 hasn't been solid on 68k. I know I struggle to find the
> > time to work on it.
>
> 2.6.17 without ADB seems pretty solid to me except for the genrtc pr
> > well we haven't had much testing here on 2.6 either, making this big jump.
>
> It's true 2.6 hasn't been solid on 68k. I know I struggle to find the
> time to work on it.
2.6.17 without ADB seems pretty solid to me except for the genrtc problems
(I do have two nice panic logs on that issue, bu
> Feel free to correct me if I'm wrong, but I don't think this was a IIfx
> or a machine with Sonic ethernet. It's possible the 5380 core code has
> suffered from bitrot. It's mostly just used by 68k. The only x86 uses
> are some old cards that I really doubt get much testing on 2.6.
I have no ide
On Fri, Oct 06, 2006 at 09:21:24PM -0700, Brian Morris wrote:
> well we haven't had much testing here on 2.6 either, making this big jump.
It's true 2.6 hasn't been solid on 68k. I know I struggle to find the
time to work on it.
> my machine, is lcIII/performa450, is supposed to be somewhat simil
Feel free to correct me if I'm wrong, but I don't think this was a IIfx
or a machine with Sonic ethernet. It's possible the 5380 core code has
suffered from bitrot. It's mostly just used by 68k. The only x86 uses
are some old cards that I really doubt get much testing on 2.6.
well we haven't ha
On Fri, Oct 06, 2006 at 03:06:37PM +0200, Michael Schmitz wrote:
> > i interpreted this exactly that way. the message comes from the scsci
> > controller. the controller is recieving commanf code 54 which besides
> > being an optional command (not part of the standard list) is not even
> > appropri
> > > i did try this, i found it was behaving rather unpredictably, once i
> > > got an error
> > > 54 not understood,
> >
> > ??? The above should go into the kernel options line of the booter, in
> > case I didn't make this clear before. "54 not understood" is nothing I
> > would expect the kerne
On 9/29/06, Michael Schmitz <[EMAIL PROTECTED]> wrote:
> > You can try to disable disconnecting - mac5380=1 or mac5380=-1,1 might
> > help.
>
> i did try this, i found it was behaving rather unpredictably, once i
> got an error
> 54 not understood,
??? The above should go into the kernel option
> > You can try to disable disconnecting - mac5380=1 or mac5380=-1,1 might
> > help.
>
> i did try this, i found it was behaving rather unpredictably, once i
> got an error
> 54 not understood,
??? The above should go into the kernel options line of the booter, in
case I didn't make this clear be
-- Forwarded message --
From: Brian Morris <[EMAIL PROTECTED]>
Date: Sep 28, 2006 10:52 PM
Subject: Re: linux-image-2.6-17-mac tries
To: Michael Schmitz <[EMAIL PROTECTED]>
On 9/21/06, Michael Schmitz <[EMAIL PROTECTED]> wrote:
> says it is SCSI 1 CCS, which stands for "Common C
23 matches
Mail list logo
