I'm don't think all of this code should move.

In particular, parts of prom_parse.c dealing with irqs handle virtual
irqs in a powerpc specific way.
I also think ifdef PPC_PSERIES and PPC_64 and PPC_32 in prom.c are
indicative of the fact that alot of this is dealing with
architecture-specific issues.

Probably some parts of these files, but it's going to take some tweezing
to figure out what parts.

Steve

quoted text
> -----Original Message-----
> From: owner-microblaze-uclinux@itee.uq.edu.au
[mailto:owner-microblaze-uclinux@itee.uq.edu.au] On
quoted text
> Behalf Of Michal Simek
> Sent: Wednesday, May 07, 2008 12:12 PM
> To: Grant Likely
> Cc: monstr@seznam.cz; microblaze-uclinux@itee.uq.edu.au;
linux-kernel@vger.kernel.org; arnd@arndb.de;
quoted text
> linux-arch@vger.kernel.org; John Linn; john.williams@petalogix.com;
matthew@wil.cx;
quoted text
> will.newton@gmail.com; drepper@redhat.com; Paul Mackerras; Stephen
Rothwell; David Miller
quoted text
> Subject: Re: [microblaze-uclinux] [PATCH 04/56] microblaze_v2: Open
firmware files
quoted text
> 
> Hi Grant,
> 
> you understand I use of_device, of_platform and prom_parse. If you do
diff
quoted text
> between them they will almost the same. One small difference is in
prom.c file.
quoted text
> 
> I hope we will move these files to drivers/of.
> This is not only question to me.
> 
> Paul, Steve and David: Can I moved these three files to drivers/of?
> 
> Michal
> 
> >> Hi Steve,
> >>
> >>  you are right. Microblaze don't need CONFIG_PPC_something but
> >>  I keep this in files because it will be easier to move this to
better place.
quoted text
> >>  I wanted to sort what Microblaze don't use.
> >>
> >>  I need to talk with people from sparc and powerpc what we can move
and where.
quoted text
> >>  I see the best way to push these files to microblaze/kernel/ and
then sychronize
quoted text
> >>  them with one patch - all archs together.
> >
> > I would disagree.  I think its better to push (and get merged)
patches
quoted text
> > to move the files first; then add microblaze on top of that.  You
can
quoted text
> > start getting stuff merged piecemeal that way instead of relying on
> > getting your entire patch series merged at once.
> >
> > However, that's just my opinion, others may look at it differently.
> >
> > Cheers,
> > g.
> >
> 
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@itee.uq.edu.au
> Project Home Page :
http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
quoted text
> Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
quoted text
> 


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