linux-kernel - Re: [RFC v4 03/25] m68k/atari: Move Atari-specific code out of drivers/char/nvram.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 22 Jul 2015 16:32:27 +0200
From:	"Christian T. Steigies" <cts@...ian.org>
To:	Finn Thain <fthain@...egraphics.com.au>
Cc:	Michael Schmitz <schmitzmic@...il.com>,
	Andreas Schwab <schwab@...ux-m68k.org>,
	linux-kernel@...r.kernel.org, linux-m68k@...r.kernel.org,
	linuxppc-dev@...ts.ozlabs.org,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Arnd Bergmann <arnd@...db.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [RFC v4 03/25] m68k/atari: Move Atari-specific code out of
 drivers/char/nvram.c

On Wed, Jul 22, 2015 at 02:22:21PM +1000, Finn Thain wrote:
> 
> 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?)

The Falcon is not powered on currently but it should still work. What should
I test?

> 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.

Christian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/