From: Michal Simek <monstr@seznam.cz>
To: microblaze-uclinux@itee.uq.edu.au
Cc: Arnd Bergmann <arnd@arndb.de>,
John Williams <john.williams@petalogix.com>,
jwboyer@linux.vnet.ibm.com, benh@kernel.crashing.org,
John Linn <linnj@xilinx.com>, git-dev <git-dev@xilinx.com>,
Grant Likely <grant.likely@secretlab.ca>, git <git@xilinx.com>,
linux-kernel@vger.kernel.org, paulus@samba.org
Subject: Re: [microblaze-uclinux] Re: Microblaze Linux release
Date: Sat, 19 Apr 2008 12:38:31 +0200 [thread overview]
Message-ID: <4809CBA7.1090508@seznam.cz> (raw)
In-Reply-To: <20080418175602.5E15E670052@mail81-sin.bigfish.com>
Hi Steve
>>> * the consistent.c implementation looks strange. Is any of that code
>>> even used anywhere? What is it good for, considering that you don't
> have
>>> an mmu?
>> We have prepared MMU code. I hope that this code for FDT kernel comes
> soon.
>> This code is written by John Williams. I have never changed it. I see
> that this
>> code solves problems around ucached_shadows stuff.
>>
> http://developer.petalogix.com/wiki/UserGuide/AdvancedTopics/EnablingUnc
> achedShadow
>> JW. Can you comment this?
>
> It probably makes sense to grab: arch/microblaze/mm/dma-coherent.c from
> git.xilinx.com and drop consistent.c. I believe this is the more
> 'modern' way to implement this functionality. I think it's easiest for
> you to just grab this file.
I'll look at it.
>>> * Your dma_mapping.h does BUG() for almost everything. I suspect you
> could
>>> easily replace it with a trivial implementation, like the x86_32
> one.
>> OK. I'll synchronize this.
>
> This is also in git.xilinx.com.
ok.
>>> * You don't seem to have any code for PCI, so the pci.h and
> pci-bridge.h
>>> files don't make much sense.
>> Yes you are right. I don't have any PCI code but I think that this
> code for MB
>> exists. Steve or John: Do you have any code for PCI?
>
> I'd recommend dropping anything having to do with PCI: I don't know that
> there is much interest in it on microblaze.
I think I'll do it
> Other comments:
>
> memset/memmove/memcpy are broken under gcc4. There are fixed versions
> of this at git.xilinx.com. Again, it's probably easiest if you just
> grab the files directly.
NO. I fixed it. The problem was different as wrote Jan Engelhardt in previous
email. Changes are in repository. You have in xilinx repository only byte copy
and huge if 1 else endif. This is not acceptable. That's only as my explanation.
> It would also be good to have irq_of_parse_and_map, which drivers will
> need. I'll send you a patch for this one.
This parts of code is coming with uartlite driver.
Thanks for your comments,
Michal
next prev parent reply other threads:[~2008-04-19 10:44 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
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 [this message]
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=4809CBA7.1090508@seznam.cz \
--to=monstr@seznam.cz \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=git-dev@xilinx.com \
--cc=git@xilinx.com \
--cc=grant.likely@secretlab.ca \
--cc=john.williams@petalogix.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linnj@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=paulus@samba.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.