Date: Wed, 15 Dec 2010 08:39:20 +0100
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, Nicolas Ferre <nicolas.ferre@atmel.com>,
        Patrice VILCHEZ <patrice.vilchez@atmel.com>
Subject: Re: [PATCH] base: add sysfs socs info
Message-ID: <20101215073920.GU19897@game.jcrosoft.org>
References: <1292330417-13703-1-git-send-email-plagnioj@jcrosoft.com>
 <20101214161130.GB1857@suse.de>
 <20101215012511.GQ19897@game.jcrosoft.org>
 <20101215034713.GB3297@suse.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20101215034713.GB3297@suse.de>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1046
Lines: 26

> > > 
> > > Also, isn't this information already in /proc/cpu/ today?
> > no all this information are not present in /proc/cpu and a cpu is not a soc
> > 
> > basicaly on a board you will have one soc but some boards have more as example
> > some ST boards you have two sh4 soc or on some amcc you have two powerpc soc
> > 
> > with these information you are allow to dynamise the userspace based on the
> > soc or the companion soc and also be able to display this information in a UI
> 
> Ok, but then why not make it "real" devices and not sysdev?  We are
> trying to fix the sysdev code to be semi-real devices, so you might as
> well make them real ones now.
ok I base my work on drivers/base/cpu.c

where we also use sysdev

can we point me a code how you want I implement it

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