From mboxrd@z Thu Jan  1 00:00:00 1970
From: Finn Thain <fthain@telegraphics.com.au>
Subject: Re: [RFC] m68k: Update defconfigs
Date: Thu, 5 Jan 2012 22:42:54 +1100 (EST)
Message-ID: <alpine.LNX.2.00.1201052212470.6601@nippy.intranet>
References: <alpine.DEB.2.00.1201042252450.15625@ayla.of.borg>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Return-path: <linux-m68k-owner@vger.kernel.org>
In-Reply-To: <alpine.DEB.2.00.1201042252450.15625@ayla.of.borg>
Sender: linux-m68k-owner@vger.kernel.org
List-Id: linux-m68k@vger.kernel.org
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@lists.linux-m68k.org>, Linux Kernel Development <linux-kernel@vger.kernel.org>, Debian GNU/Linux m68k <debian-68k@lists.debian.org>


On Wed, 4 Jan 2012, Geert Uytterhoeven wrote:

> Findings:
>   - CONFIG_BLK_DEV_SWIM is m, while CONFIG_AMIGA_FLOPPY and
>     CONFIG_ATARI_FLOPPY are y.

My defconfig patch used "m" because (if I recall correctly) the SWIM 
driver is experimental code that couldn't be safely loaded on all 
machines.

>   - Amiga and Atari use CONFIG_RTC_CLASS, the others don't.
>     Should we switch everything to CONFIG_RTC_CLASS (and thus drop
>     CONFIG_GEN_RTC)? We do have CONFIG_RTC_DRV_GENERIC now.

This would alter the device major/minor numbers and devtmpfs path, right?

Also I wonder about CONFIG_RTC_HCTOSYS on Macs without a working RTC 
driver. Would enabling CONFIG_RTC_HCTOSYS change present behaviour?

I suppose it might need some testing. Otherwise, I think harmonising this 
across defconfigs (and distro configs) is a good idea.

Finn