linux-kernel - RE: [PATCH 10/56] microblaze_v2: Generic dts file for platforms

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 5 May 2008 16:32:36 -0700
From:	"Stephen Neuendorffer" <stephen.neuendorffer@...inx.com>
To:	"John Williams" <john.williams@...alogix.com>
Cc:	<monstr@...nam.cz>, <linux-kernel@...r.kernel.org>,
	<arnd@...db.de>, <linux-arch@...r.kernel.org>,
	"John Linn" <linnj@...inx.com>, <matthew@....cx>,
	<will.newton@...il.com>, <drepper@...hat.com>,
	<microblaze-uclinux@...e.uq.edu.au>, <grant.likely@...retlab.ca>,
	"Michal Simek" <monstr@...str.eu>
Subject: RE: [PATCH 10/56] microblaze_v2: Generic dts file for platforms


The .dts is not board specific, it's design specific.  In my opinion,
this is not something that 'a vendor might maintain multiple versions
of': instead it is in most cases simply fundamental to the FPGA design
flow.  In fact, in most cases, I'd like to make the .dts file part of
the bitstream and not compiled into the kernel.

Although powerpc has a bit more boot-time complexity than the microblaze
does currently, I think it makes alot of sense to have some consistency
here, and there is already a pattern to follow here which nicely
orthogonalizes multiple .dts files for the same platform code.

Steve

> -----Original Message-----
> From: John Williams [mailto:john.williams@...alogix.com]
> Sent: Monday, May 05, 2008 4:17 PM
> To: Stephen Neuendorffer
> Cc: monstr@...nam.cz; linux-kernel@...r.kernel.org; arnd@...db.de;
linux-arch@...r.kernel.org; John
> Linn; matthew@....cx; will.newton@...il.com; drepper@...hat.com;
microblaze-uclinux@...e.uq.edu.au;
> grant.likely@...retlab.ca; Michal Simek
> Subject: RE: [PATCH 10/56] microblaze_v2: Generic dts file for
platforms
> 
> On Mon, 2008-05-05 at 10:25 -0700, Stephen Neuendorffer wrote:
> > I think it would be nice if dts files were stored in boot/dts, as on
> > powerpc, which would reduce confusion.
> 
> I'm not so sure.  By grouping
> 
>  * the DTS
>  * Kconfig.auto (now just storing CPU parameters for CPUFLAGS); and
>  * board-specific setup.c if required,
> 
> we concentrate in one place, in a single subdir of
> arch/microblaze/platform/*, all of the board specific info.
> 
> Maybe our Kbuild should copy the platform .dts file out of the
platform
> dir and into microblaze/boot, like we do with the finished kernel?
Then
> it's ready to be picked up by the user or some higher level build
tool.
> 
> If users or vendors want to maintain multiple DTS files for a single
> board, again they can just collect them in the platform subdir so
their
> intended target remains obvious.
> 
> John
> 
> 
> >
> > Steve
> >
> > > -----Original Message-----
> > > From: monstr@...nam.cz [mailto:monstr@...nam.cz]
> > > Sent: Sunday, May 04, 2008 4:41 AM
> > > To: linux-kernel@...r.kernel.org
> > > Cc: arnd@...db.de; linux-arch@...r.kernel.org; Stephen
Neuendorffer;
> > John Linn;
> > > john.williams@...alogix.com; matthew@....cx;
will.newton@...il.com;
> > drepper@...hat.com; microblaze-
> > > uclinux@...e.uq.edu.au; grant.likely@...retlab.ca; Michal Simek
> > > Subject: [PATCH 10/56] microblaze_v2: Generic dts file for
platforms
> > >
> > > From: Michal Simek <monstr@...str.eu>
> > >
> > >
> > > Signed-off-by: Michal Simek <monstr@...str.eu>
> > > ---
> > >  arch/microblaze/platform/generic/system.dts |  137
> > +++++++++++++++++++++++++++
> > >  1 files changed, 137 insertions(+), 0 deletions(-)
> > >  create mode 100644 arch/microblaze/platform/generic/system.dts
> >
> --
> John Williams, PhD, B.Eng, B.IT
> PetaLogix - Linux Solutions for a Reconfigurable World
> w: www.petalogix.com  p: +61-7-30090663  f: +61-7-30090663
> 
> 


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