LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC v6 00/25] Re-use nvram module
Date: Mon, 12 Oct 2015 13:32:06 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LNX.2.00.1510121326110.23992@nippy.intranet> (raw)
In-Reply-To: <561AC137.9090809@redhat.com>


Hi Laurent,

On Sun, 11 Oct 2015, Laurent Vivier wrote:
> On 23/08/2015 12:41, Finn Thain wrote:
...
> > This patch series has been compile-tested for arm, m68k, powerpc and 
> > x86. The nvram and thinkpad_acpi modules were regression tested on a 
> > ThinkPad T43. The /dev/nvram functionality was also regression tested 
> > on a G3 PowerMac. The nvram module was also tested on a PowerBook 520, 
> > Quadra 650 and Atari Falcon. AFAIK, no testing has been done on PPC64 
> > as yet.
> 
> For PPC64, tested on a PowerMac G5 (PowerMac11,2), kernel 4.3.0-rc4
> with nvram tools 1.2.24 (Fedora 22 ppc64).
> 
> Tested-by: Laurent Vivier <lvivier@redhat.com>
> 
> Tests done:
>  # modinfo nvram
>  filename:       /lib/modules/4.3.0-rc4+/kernel/drivers/char/nvram.ko
>  alias:          devname:nvram
>  alias:          char-major-10-144
>  license:        GPL
>  depends:
>  intree:         Y
>  vermagic:       4.3.0-rc4+ SMP mod_unload
> 
>  # modprobe nvram
>  [  364.655577] Non-volatile memory driver v1.3
> 
>  # nvram --partitions
>   # Sig Chk  Len  Name
>   0  5a  82  0002 nvram
>   1  5f  45  003e system
>   2  70  bd  00c1 common
>   3  a0  1e  0052 APL,MacOS75
>   4  a1  15  0081 APL,OSXPanic
>   5  7f  45  002c wwwwwwwwwwww
> 
>  # nvram --dump "nvram"
>  0x00000000  5a820002 6e767261 6d000000 00000000 |Z...nvram.......|
>  0x00000010  cae8613d 000001c9 00000000 00000000 |..a=............|
> 
>  # nvram --print-config=boot-volume
>  1
> 
>  # nvram --update-config=boot-volume=6
> 
>  # rmmod nvram
> 
>  # nvram --print-config=boot-volume
>  6
> 
>  # reboot
> 
>  # nvram --print-config=boot-volume
>  6
> 

Thanks very much for taking the trouble to test this series.

I will add your Tested-By tag to the relevant powerpc patches and re-send.

Regards,
Finn

      reply	other threads:[~2015-10-12  2:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-23 10:41 [RFC v6 00/25] Re-use nvram module Finn Thain
2015-08-23 10:41 ` [RFC v6 01/25] scsi/atari_scsi: Dont select CONFIG_NVRAM Finn Thain
2015-08-23 10:41 ` [RFC v6 02/25] m68k/atari: Move Atari-specific code out of drivers/char/nvram.c Finn Thain
2015-08-23 10:41 ` [RFC v6 03/25] m68k/atari: Replace nvram_{read, write}_byte with arch_nvram_ops Finn Thain
2015-10-14 11:19   ` [RFC v6 03/25] m68k/atari: Replace nvram_{read,write}_byte " Finn Thain
2015-08-23 10:41 ` [RFC v6 04/25] char/nvram: Re-order functions to remove forward declarations and #ifdefs Finn Thain
2015-08-23 10:41 ` [RFC v6 05/25] char/nvram: Adopt arch_nvram_ops Finn Thain
2015-08-23 10:41 ` [RFC v6 06/25] x86/thinkpad_acpi: Use arch_nvram_ops methods instead of nvram_read_byte() and nvram_write_byte() Finn Thain
2015-08-23 10:41 ` [RFC v6 07/25] char/nvram: Allow the set_checksum and initialize ioctls to be omitted Finn Thain
2015-08-23 10:41 ` [RFC v6 08/25] char/nvram: Implement NVRAM read/write methods Finn Thain
2015-08-23 10:41 ` [RFC v6 09/25] char/nvram: Use generic fixed_size_llseek() Finn Thain
2015-08-23 10:41 ` [RFC v6 10/25] m68k/atari: Implement arch_nvram_ops methods and enable CONFIG_HAVE_ARCH_NVRAM_OPS Finn Thain
2015-08-23 10:41 ` [RFC v6 11/25] char/nvram: Add "devname:nvram" module alias Finn Thain
2015-08-23 10:41 ` [RFC v6 12/25] powerpc: Cleanup nvram includes Finn Thain
2015-08-23 10:41 ` [RFC v6 13/25] powerpc: Add missing ppc_md.nvram_size for CHRP and PowerMac Finn Thain
2015-08-23 10:41 ` [RFC v6 14/25] powerpc: Implement arch_nvram_ops.get_size() and remove old nvram_* exports Finn Thain
2015-08-23 10:41 ` [RFC v6 15/25] powerpc: Implement nvram sync ioctl Finn Thain
2015-08-23 10:41 ` [RFC v6 16/25] powerpc, fbdev: Use NV_CMODE and NV_VMODE only when CONFIG_PPC32 and CONFIG_PPC_PMAC and CONFIG_NVRAM Finn Thain
2015-08-23 10:41 ` [RFC v6 17/25] powerpc, fbdev: Use arch_nvram_ops methods instead of nvram_read_byte() and nvram_write_byte() Finn Thain
2015-08-23 10:41 ` [RFC v6 18/25] nvram: Drop nvram_* symbol exports and prototypes Finn Thain
2015-08-23 10:41 ` [RFC v6 19/25] powerpc: Remove CONFIG_GENERIC_NVRAM and adopt CONFIG_HAVE_ARCH_NVRAM_OPS Finn Thain
2015-08-23 10:41 ` [RFC v6 20/25] char/generic_nvram: Remove as unused Finn Thain
2015-08-23 10:41 ` [RFC v6 21/25] powerpc: Adopt nvram module for PPC64 Finn Thain
2015-08-23 10:41 ` [RFC v6 22/25] m68k/mac: Adopt naming and calling conventions for PRAM routines Finn Thain
2015-08-23 10:41 ` [RFC v6 23/25] m68k/mac: Use macros for RTC accesses not magic numbers Finn Thain
2015-08-23 10:41 ` [RFC v6 24/25] m68k/mac: Fix PRAM accessors Finn Thain
2015-08-23 10:41 ` [RFC v6 25/25] m68k: Dispatch nvram_ops calls to Atari or Mac functions Finn Thain
2015-10-11 20:06 ` [RFC v6 00/25] Re-use nvram module Laurent Vivier
2015-10-12  2:32   ` Finn Thain [this message]

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=alpine.LNX.2.00.1510121326110.23992@nippy.intranet \
    --to=fthain@telegraphics.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lvivier@redhat.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