On Wed, 22 Jul 2015, Michael Schmitz wrote:
Hi Finn,
I'm afraid I cannot test anything on Atari hardware at present - my
Falcon ate it's IDE disk partition table with all the fun that entails.
That doesn't sound good.
Haven't even begun to try and recover that yet.
If you send a patch I could build a kernel and send that to Christian
for testing (if he's got his Falcon up and running - might be a tad warm
in the attic for that, in fact).
Anyone with a suitable Atari, i.e. ATARIHW_PRESENT(TT_CLK), who can boot
both TOS and Linux could resolve the question. (Perhaps with an emulator?)
Any old kernel binary would do, since atari_scsi should print either
"HOSTID=n" or "this_id n" at startup.
If n doesn't agree with what TOS says about the host's SCSI ID, then I
think a trivial patch is safe enough. Especially if cat /proc/driver/nvram
produces a "SCSI host ID : m" that does agree with TOS.
Regards,
Finn
Cheers,
Michael
Am 14.07.15 um 20:17 schrieb Finn Thain:
On Mon, 13 Jul 2015, Andreas Schwab wrote:
Finn Thain <fthain@xxxxxxxxxxxxxxxxxxx> writes:
BTW, I didn't change the SCSI ID location in NVRAM. This code says 16
whereas atari_scsi says 14. Which one is correct?
I think atari_scsi is wrong. The best source I could find
(http://www.gratifiant.com/nvram-falcon-t561185) places it after the
video mode byte, thus at byte 16.
Thanks for that. BTW, I googled a phrase from that page and found this one
http://toshyp.atari.org/en/004009.html
which may be closer to the source.
I'll send a patch if someone can offer to test such a change to atari_scsi
(or merely confirm that the SCSI ID setting in TOS does not match this_id
given in dmesg).
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
