From: John Williams <john.williams@petalogix.com>
To: monstr@seznam.cz
Cc: Florian Fainelli <florian.fainelli@telecomint.eu>,
Arnd Bergmann <arnd@arndb.de>, Paul Mackerras <paulus@samba.org>,
benh@kernel.crashing.org,
Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>,
jwboyer@linux.vnet.ibm.com, John Linn <John.Linn@xilinx.com>,
git-dev@xilinx.com, Grant Likely <grant.likely@secretlab.ca>,
git@xilinx.com, microblaze-uclinux@itee.uq.edu.au,
linux-kernel@vger.kernel.org
Subject: Re: Microblaze Linux release
Date: Thu, 24 Apr 2008 08:51:17 +1000 [thread overview]
Message-ID: <1208991077.3050.141.camel@localhost> (raw)
In-Reply-To: <480FA8A4.7020207@seznam.cz>
Hi,
On Wed, 2008-04-23 at 23:22 +0200, Michal Simek wrote:
> > Hi Michal
> >
> >> Hi all,
> >>
> >> I update Microblaze kernel to latest Linus tree. I fixed some problems
> >> which come with it.
> >
> > While reading the previous discussion, I wondered that keeping PCI would be a
> > good idea. I am personnaly using it for a custom design and would be glad
> > being able to continue using it.
>
> I'll add PCI parts as I will have a reason to do it. I have no PCI devices
> connected to MB now.
>
> > If this represents too much work for you, we can probably add it later.
>
> yes. This is lot of work for me unfortunately without any commercial support.
>
> > Great work !
I have a working PCI implementation that I will submit once Michal's
patches are finalised.
Unsurprisingly it is heavily derived from the PPC implementation, but
reworked a little bit.
Regards,
John
>
> Have a good day,
> Michal Simek
--
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
next prev parent reply other threads:[~2008-04-23 23:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 13:26 Microblaze Linux release Michal Simek
2008-04-13 13:33 ` Grant Likely
2008-04-13 15:44 ` Michal Simek
2008-04-13 15:13 ` Josh Boyer
2008-04-13 18:50 ` Michal Simek
2008-04-14 15:55 ` Stephen Neuendorffer
2008-04-15 12:59 ` Michal Simek
2008-04-14 3:38 ` Arnd Bergmann
2008-04-14 5:10 ` H. Peter Anvin
2008-04-14 6:55 ` Arnd Bergmann
2008-04-14 6:01 ` Arnd Bergmann
2008-04-15 12:54 ` Michal Simek
2008-04-15 13:32 ` Arnd Bergmann
2008-04-15 21:52 ` Benjamin Herrenschmidt
2008-04-16 6:24 ` Michal Simek
2008-04-16 7:31 ` Paul Mackerras
2008-04-16 7:44 ` Arnd Bergmann
2008-04-16 15:28 ` Michal Simek
2008-04-16 15:33 ` Arnd Bergmann
2008-04-23 20:55 ` Michal Simek
2008-04-23 20:57 ` Florian Fainelli
2008-04-23 21:01 ` Arnd Bergmann
2008-04-23 21:08 ` Michal Simek
2008-04-23 21:22 ` Michal Simek
2008-04-23 22:51 ` John Williams [this message]
2008-04-16 15:26 ` Michal Simek
2008-04-16 7:45 ` Benjamin Herrenschmidt
2008-04-23 21:35 ` Michal Simek
2008-04-23 20:57 ` Michal Simek
2008-04-18 17:56 ` [microblaze-uclinux] " Stephen Neuendorffer
2008-04-19 10:38 ` Michal Simek
2008-04-14 7:10 ` Michal Simek
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=1208991077.3050.141.camel@localhost \
--to=john.williams@petalogix.com \
--cc=John.Linn@xilinx.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=florian.fainelli@telecomint.eu \
--cc=git-dev@xilinx.com \
--cc=git@xilinx.com \
--cc=grant.likely@secretlab.ca \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@seznam.cz \
--cc=paulus@samba.org \
--cc=stephen.neuendorffer@xilinx.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