From: Alan Hourihane <alanh@fairlite.co.uk>
To: Michael Schmitz <schmitzmic@googlemail.com>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Atari TT (next)
Date: Mon, 09 Jan 2012 01:03:26 +0000 [thread overview]
Message-ID: <4F0A3CDE.7070308@fairlite.co.uk> (raw)
In-Reply-To: <CAOmrzk+P3mPXu_Q_KxgEk_jx-JNhXY4ydrKoGM+43LpD5icTHw@mail.gmail.com>
On 09/01/12 00:05, Michael Schmitz wrote:
> What buffers? Filesystem buffers should be fine in TT-RAM. atafb
> buffer requirement could be reduced by using a low-res video mode
> perhaps (just to get past this point initially).
O.k. I've managed to cut down the kernel and boot with atafb enabled and
it works, using the stram_pool option.
Next problem is the SCSI controller.
I get......
Atari SCSI: resetting the SCSI bus... done
scsi0: options CAN_QUEUE=16 CMD_PER_LUN=8 SCAT-GAT=128 TAGGED-QUEUING=no
HOSTID=7 generic options AUTOSENSE REAL DMA SCSI-2 TAGGED QUEUING
generic release=7
scsi0 : Atari native SCSI
scsi0: aborting command
scsi 0:0:0:0: CDB: Inquiry: 12 00 00 00 24 00
NCR5380 core release=7.
NCR5380: coroutine isn't running.
scsi0: no currently connected command
scsi0: issue_queue
scsi0: disconnected_queue
scsi0: destination target 0, lun 0
command = 18 (0x12) 00 00 00 24 00
NCR5380 core release=7.
NCR5380: coroutine isn't running.
scsi0: no currently connected command
scsi0: issue_queue
scsi0: disconnected_queue
scsi0: destination target 0, lun 0
command = 18 (0x12) 00 00 00 24 00
scsi 0:0:0:0: Device offlined - not ready after error recovery
I'll start poking at this.
Alan.
next prev parent reply other threads:[~2012-01-09 1:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 1:27 Atari TT (next) Alan Hourihane
2012-01-07 6:47 ` Michael Schmitz
2012-01-07 16:59 ` Alan Hourihane
2012-01-08 0:46 ` Alan Hourihane
2012-01-08 4:13 ` Michael Schmitz
2012-01-08 9:35 ` Andreas Schwab
2012-01-08 9:42 ` Alan Hourihane
2012-01-08 23:51 ` Michael Schmitz
2012-01-08 23:59 ` Alan Hourihane
2012-01-09 0:05 ` Michael Schmitz
2012-01-09 0:14 ` Alan Hourihane
2012-01-09 0:23 ` Andreas Schwab
2012-01-09 3:17 ` Michael Schmitz
2012-01-09 1:03 ` Alan Hourihane [this message]
2012-01-09 1:25 ` Alan Hourihane
2012-01-09 10:40 ` Andreas Schwab
2012-01-09 11:22 ` Alan Hourihane
2012-01-09 12:14 ` Geert Uytterhoeven
2012-01-09 12:40 ` Tuomas Vainikka
2012-01-09 14:10 ` [PATCH] m68k: fix assembler constraint to prevent overeager gcc optimisation Andreas Schwab
2012-01-22 10:15 ` Geert Uytterhoeven
2012-01-22 10:53 ` Geert Uytterhoeven
2012-01-22 12:42 ` Andreas Schwab
2012-01-09 3:16 ` Atari TT (next) Michael Schmitz
2012-01-27 17:01 ` Thorsten Glaser
2012-01-28 20:33 ` Michael Schmitz
2012-01-29 0:57 ` Thorsten Glaser
2012-01-29 9:42 ` Geert Uytterhoeven
2012-01-29 19:55 ` Thorsten Glaser
2012-01-29 21:56 ` Geert Uytterhoeven
2012-01-08 10:20 ` Geert Uytterhoeven
2012-01-08 19:21 ` Michael Schmitz
2012-01-08 19:53 ` Geert Uytterhoeven
2012-01-08 23:42 ` Michael Schmitz
2012-01-08 22:05 ` Andreas Schwab
2012-01-08 23:39 ` Michael Schmitz
2012-01-08 23:49 ` Alan Hourihane
2012-01-08 23:58 ` Michael Schmitz
2012-01-08 13:36 ` Andreas Schwab
2012-01-08 14:42 ` Alan Hourihane
2012-01-08 19:24 ` Michael Schmitz
2012-01-08 17:45 ` Geert Uytterhoeven
2012-01-08 19:50 ` Alan Hourihane
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=4F0A3CDE.7070308@fairlite.co.uk \
--to=alanh@fairlite.co.uk \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@googlemail.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