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

[Michael Schmitz]

Finn,

my bad - there is indeed a change in the /proc/driver/nvram output:

--- nvram-4.out    2015-07-24 12:32:44.000000000 +1200
+++ nvram-4p2.out    2015-07-27 13:56:06.000000000 +1200
@@ -7,7 +7,7 @@
 Keyboard language: English (US)
 Date format      : DD.MM.YY, 24h clock
 Boot delay       : 32s
-Video mode       : 4 colors, 40 columns, TV NTSC monitor
+Video mode       : 256 colors, 80 columns, VGA PAL monitor
                    no overscan, compat. mode off
 00000000  00 00 00 00 00 00 00 00  11 2e 20 01 ff 00 00 3b  |.......... ....;|
 00000010  84 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|


That video mode is indeed the one set in the NVRAM (by ARAnyM config,
if running emulated)

Cheers,

  Michael


On Sun, Jul 26, 2015 at 1:19 PM, Finn Thain <fthain at telegraphics.com.au> wrote:
>
> On Sun, 26 Jul 2015, Michael Schmitz wrote:
>
>> Hi Finn,
>>
>> For the sake of completeness: further testing on ARAnyM shows no difference
>> between original and patched kernel in the NVRAM proc and diff outputs:
>>
>> scsi host0: Atari native SCSI, io_port 0x0, n_io_port 0, base 0x0, irq 15,
>> can_queue 8, cmd_per_lun 1, sg_tablesize 0, this_id 7, flags { }, options {
>> REAL_DMA SUPPORT_TAGS }
>> Checksum status  : valid
>> Boot preference  : unspecified
>> SCSI arbitration : on
>> SCSI host ID     : 7
>> OS language      : English (US)
>> Keyboard language: English (US)
>> Date format      : DD.MM.YY, 24h clock
>> Boot delay       : 32s
>> Video mode       : 4 colors, 40 columns, TV NTSC monitor
>>                    no overscan, compat. mode off
>> 00000000  00 00 00 00 00 00 00 00  11 2e 20 01 ff 00 00 3b |.......... ....;|
>> 00000010  87 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|
>> 00000020  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 |................|
>> 00000030  de 21                                            |.!|
>> 00000032
>
> I'd expect to see a change in the Video mode above, because of patch 2.
>
> With 0x3B in byte 15, I'd expect the patched kernel to produce something
> similar to Christian's /proc/driver/nvram results.
>
> --