Microblaze Linux release
Hi Everybody,
I fixed all reported bugs which I got from LKML and from you. Latest version of Microblaze Linux kernel is available at git.monstr.eu. There is git repository called linux-microblaze.git
Microblaze port is based on 2.6.24-rc5. I'll create the new repo with clean pack of changes based on latest kernel version for easier pull.
Merge windows will be open hopefully next week and I would like to send pull request to Paul.
I would like to ask you for review all microblaze code especially arch/microblaze and include/asm-microblaze. Please don't send me question to drivers - Microblaze will use only uartlite driver (only add on or to Kconfig - that's enough for now).
All questions and reported bug please send to me.
Please report all bugs (coding style, long line, poor coments - everything). Please send me your ACK too. For my better summary - please send me list of files. Summary will be continuously concurrently publish at
http://www.monstr.eu/wiki/doku.php?id=kernel:kernel.
Thanks for your help,
Michal Simek,
www.monstr.eu
P.S.: For LKML users - I am going to integrate all bugs to previous set of patches - that's why I asked about how to do it. I hope I send this pack today or on Monday.
Quoted 8 lines · Michal Simek
Hi Everybody,
I fixed all reported bugs which I got from LKML and from you. Latest version of Microblaze Linux kernel is available at git.monstr.eu. There is git repository called linux-microblaze.git
Microblaze port is based on 2.6.24-rc5. I'll create the new repo with clean pack of changes based on latest kernel version for easier pull.
Quoted 7 lines
Merge windows will be open hopefully next week and I would like to send pull request to Paul.
I would like to ask you for review all microblaze code especially
arch/microblazeandinclude/asm-microblaze. Please don't send me question to drivers - Microblaze will use only uartlite driver (only add on or toKconfig- that's enough for now).
Can you please also post your updated patch series? Reviewing patches is easy. Reviewing a git tree is a lot more work.
Thanks,
g.
Signature · 2 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.
Hi Grant,
as I wrote. I am working on it. I'll send them ASAP.
Michal
Quoted 22 lines
Quoted 8 lines
Hi Everybody,
I fixed all reported bugs which I got from LKML and from you. Latest version of Microblaze Linux kernel is available at git.monstr.eu. There is git repository called linux-microblaze.git
Microblaze port is based on 2.6.24-rc5. I'll create the new repo with clean pack of changes based on latest kernel version for easier pull.Quoted 7 lines
Merge windows will be open hopefully next week and I would like to send pull request to Paul.
I would like to ask you for review all microblaze code especially
arch/microblazeandinclude/asm-microblaze. Please don't send me question to drivers - Microblaze will use only uartlite driver (only add on or toKconfig- that's enough for now).Can you please also post your updated patch series? Reviewing patches is easy. Reviewing a git tree is a lot more work.
Thanks,
g.
Quoted 10 lines · On Sun, 13 Apr 2008 15:26:57 +0200 Michal Simek <[email protected]> wrote:
Hi Everybody,
I fixed all reported bugs which I got from LKML and from you. Latest version of Microblaze Linux kernel is available at git.monstr.eu. There is git repository called linux-microblaze.git
Microblaze port is based on 2.6.24-rc5. I'll create the new repo with clean pack of changes based on latest kernel version for easier pull.Merge windows will be open hopefully next week and I would like to send pull request to Paul.
Why Paul? If microblaze is a new architecture (which it seems to be), then you should really work through Linus directly.
Also, which version of gcc/binutils are needed to actually build this?
josh
Hi Josh,
Quoted 8 lines
Quoted 8 lines
Hi Everybody,
I fixed all reported bugs which I got from LKML and from you. Latest version of Microblaze Linux kernel is available at git.monstr.eu. There is git repository called linux-microblaze.git
Microblaze port is based on 2.6.24-rc5. I'll create the new repo with clean pack of changes based on latest kernel version for easier pull.
Quoted 5 lines
Quoted 2 lines
Merge windows will be open hopefully next week and I would like to send pull request to Paul.
Why Paul? If microblaze is a new architecture (which it seems to be), then you should really work through Linus directly.
I don't know who start with it. For me is not this point important. I think that was Steve's idea, wasn't it?
Quoted 1 line
Also, which version of gcc/binutils are needed to actually build this?
I personally use gcc from Petalogix distribution. For non-MMU kernel v3.4.1. for MMU kernel I think 4.1.1. (MMU port for Microblaze FDT kernel will come later). You can download whole distribution from developer.petalogix.com.
Michal Simek
www.monstr.eu
Quoted 7 lines
-----Original Message-----
From: Michal Simek [mailto:[email protected]]
Sent: Sunday, April 13, 2008 11:51 AM
To: Josh Boyer
Cc: Stephen Neuendorffer; John Williams; [email protected];
John Linn; git-dev; Grant Likely;
Quoted 1 line
Quoted 8 lines
Subject: Re: Microblaze Linux release
Hi Josh,
Quoted 4 lines
Quoted 4 lines
Hi Everybody,
I fixed all reported bugs which I got from LKML and from you. Latest version of Microblaze Linux kernel is available at
git.monstr.eu.
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
There is git repository called linux-microblaze.git Microblaze port is based on 2.6.24-rc5. I'll create the new repo
with clean pack
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
of changes based on latest kernel version for easier pull.
Merge windows will be open hopefully next week and I would like to
send pull
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
request to Paul.
Why Paul? If microblaze is a new architecture (which it seems to
be),
Quoted 4 lines
Quoted 1 line
then you should really work through Linus directly.
I don't know who start with it. For me is not this point important. I think that was Steve's idea, wasn't it?
Nope, it should go through Linus. My hope was to recruit reviewers from the powerpc community, since there is alot of overlap (device trees, drivers, the MMU is very similar).
Steve
Hi Steve,
Quoted 18 lines
Quoted 6 lines
Hi Josh,
Quoted 4 lines
Quoted 4 lines
Hi Everybody,
I fixed all reported bugs which I got from LKML and from you. Latest version of Microblaze Linux kernel is available at
git.monstr.eu.
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
There is git repository called linux-microblaze.git Microblaze port is based on 2.6.24-rc5. I'll create the new repo
with clean pack
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
of changes based on latest kernel version for easier pull.
Merge windows will be open hopefully next week and I would like to
send pull
Quoted 2 lines
Quoted 2 lines
Quoted 1 line
request to Paul.
Why Paul? If microblaze is a new architecture (which it seems to
be),
Quoted 1 line
Quoted 1 line
then you should really work through Linus directly.
Quoted 8 lines
Quoted 2 lines
I don't know who start with it. For me is not this point important. I think that was Steve's idea, wasn't it?
Nope, it should go through Linus. My hope was to recruit reviewers from the powerpc community, since there is alot of overlap (device trees, drivers, the MMU is very similar).
Steve
That can be my mistake. I don't remember who was it. It doesn't matter.
We talked about recruits with Steve that was different topic not this.
Regards,
Michal Simek
www.monstr.eu
Quoted 4 lines · Michal Simek
I would like to ask you for review all microblaze code especially
arch/microblazeandinclude/asm-microblaze. Please don't send me question to drivers - Microblaze will use only uartlite driver (only add on or toKconfig- that's enough for now).
I'm certainly willing to help review it, but I think the timing is too short for asking for a 2.6.26 merge. Judging from experience, a new architecture review takes a few weeks to sort out all the issues you want resolved before merging, so posting them now would put you in a much more comfortable position when targeting a 2.6.27 merge.
One of the things I always wanted to have is a common location for all the things that get duplicated verbatim into each new architecture, like all the include/asm/{fcntl,ioctls,ipcbuf,mman,poll,posix_types,sem_buf}.h and others that define part of the syscall ABI.
Arnd <><
Quoted 6 lines · Arnd Bergmann
One of the things I always wanted to have is a common location for all the things that get duplicated verbatim into each new architecture, like all the
include/asm/{fcntl,ioctls,ipcbuf,mman,poll,posix_types,sem_buf}.hand others that define part of the syscall ABI.
include/asm-generic
-hpa
Quoted 9 lines · H. Peter Anvin
Quoted 6 lines · Arnd Bergmann
One of the things I always wanted to have is a common location for all the things that get duplicated verbatim into each new architecture, like all the
include/asm/{fcntl,ioctls,ipcbuf,mman,poll,posix_types,sem_buf}.hand others that define part of the syscall ABI.
include/asm-generic
Sure. Halfway through writing my sentence, I wanted to suggest arch/generic for the stuff in there that has the potential of being unified, but then realized how little there is of that, and that it may just as well go into the top-level mm/, kernel/, lib/ etc, as we have done in the past.
Arnd <><
Quoted 5 lines · Arnd Bergmann
I'm certainly willing to help review it, but I think the timing is too short for asking for a 2.6.26 merge. Judging from experience, a new architecture review takes a few weeks to sort out all the issues you want resolved before merging, so posting them now would put you in a much more comfortable position when targeting a 2.6.27 merge.
I've just looked at your git tree, and it confirmed my point that we need a little more time. Please don't hesitate to submit patches to the mailing list though. You may have misunderstood the idea of the merge window: The patches can go in during that time if they have been reviewed before, so it is not the time to post patches for review.
More to the point, here are a few things that I noticed on a brief review:
* Your arch code in general looks nice and clean, don't worry too much about the coding style right now.
* The code level is 2.6.24-rc8, while the current head is at 2.6.25-rc9. You should really upgrade the kernel level, because a number of changes have gone in that directly affect your code. Your best bet is probably now to have a patch against the linux-next tree, which also has the changes that will go into 2.6.26.
* Your syscall ABI is largely obsolete. A third of the syscalls you define should not even be there in the first place as they have been replaced by newer versions. E.g. you have select, _newselect and pselect6, where just pselect6 would be sufficient -- you don't need to worry about backwards compatibility if you don't have existing code. A good start would be to take the arch/blackfin syscall list and further reduce it from there. Further examples are:
- replace socketcall with separate syscall entry points
- replace ipc with a separate entry points
- remove all the legacy signal handling from arch/microblaze/kernel/signal.c
- remove sys_mmap, sys_olduname and sys_vfork
- finally define a generic sys_mmap2 and sys_uname in kernel/ so you don't need another copy in arch/microblaze/kernel
- Use 64 bit off_t, and 32 bit uid_t, gid_t etc.
* Your device tree functions in of_device.c, of_platform.c, prom.c and prom_parse.c are basically copies of the powerpc versions. This duplication is not helpful, better merge that code into new files in drivers/of/ so that it can be shared.
* The semaphore implementation will be obsolete in 2.6.26
* The EXPORT_SYMBOL definitions for csum_partial etc should be in arch/microblaze/lib/checksum.c, not in microblaze_ksyms.c, same for memcpy/memmove/memset.
* The platform directory is noticably empty. You can probably judge better how much platform specific code there will be in the future, but I would suspect that you're better off with a flat platform directory instead of subdirectories below that.
* 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?
* 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.
* I'm not sure if you really need something as sophisticated as the lmb code, if you don't have a real firmware, or even an MMU. setup_memory can probably work with something much simpler, and for the prom.c stuff, you may get away with #defining them to bootmem_alloc etc.
* You don't seem to have any code for PCI, so the pci.h and pci-bridge.h files don't make much sense.
* The following files:atomic.h checksum.h io.h ioctl.h ioctls.h ipcbuf.h msgbuf.h param.h poll.h posix_types.h sembuf.h shmbuf.h shmparam.h sigcontext.h signal.h socket.h sockios.h stat.h termbits.h termios.h types.h ucontext.h all look like verbatim copies of some other architecture. Please do the next person to come up with a new architecture a favor and stick them in include/asm-generic instead, including them from your own headers.
* You unistd.h contains _syscall* macros. These were removed some time ago from all other architectures.
* You define a lot of __ARCH_WANT_SYS_ macros. Generally, these are for the syscalls you don't want.
* You are missing a include/asm-microblaze/Kbuild file that lists all the header files you want to export to user space.
Arnd <><
Hi Arnd,
Quoted 12 lines
Quoted 5 lines
I'm certainly willing to help review it, but I think the timing is too short for asking for a 2.6.26 merge. Judging from experience, a new architecture review takes a few weeks to sort out all the issues you want resolved before merging, so posting them now would put you in a much more comfortable position when targeting a 2.6.27 merge.
I've just looked at your git tree, and it confirmed my point that we need a little more time. Please don't hesitate to submit patches to the mailing list though. You may have misunderstood the idea of the merge window: The patches can go in during that time if they have been reviewed before, so it is not the time to post patches for review.
Quoted 5 lines
More to the point, here are a few things that I noticed on a brief review:
* Your arch code in general looks nice and clean, don't worry too much about the coding style right now.
I think so. I spent a lot of time to clean the code.
Quoted 5 lines
* The code level is 2.6.24-rc8, while the current head is at 2.6.25-rc9. You should really upgrade the kernel level, because a number of changes have gone in that directly affect your code. Your best bet is probably now to have a patch against the linux-next tree, which also has the changes that will go into 2.6.26.
I am working on 2.6.25-rc9 Microblaze version. I am solving issue about CONFIG_HZ and new syscall timerfd_... . There are new 3 syscalls. And I think that these syscalls bring up failure to MB code.
Quoted 6 lines
* Your syscall ABI is largely obsolete. A third of the syscalls you define should not even be there in the first place as they have been replaced by newer versions. E.g. you have select,
_newselectand pselect6, where just pselect6 would be sufficient -- you don't need to worry about backwards compatibility if you don't have existing code. A good start would be to take thearch/blackfinsyscall list and further reduce it
Quoted 8 lines
from there. Further examples are:
- replace socketcall with separate syscall entry points
- replace ipc with a separate entry points
- remove all the legacy signal handling fromarch/microblaze/kernel/signal.c
- removesys_mmap,sys_oldunameandsys_vfork
- finally define a genericsys_mmap2andsys_unameinkernel/so you don't need another copy inarch/microblaze/kernel
- Use 64 bitoff_t, and 32 bituid_t,gid_tetc.
This kernel don't need to keep backward compatibility. No one will port to previous version. I'll look at your points and I'll send you what I do.
Quoted 4 lines
* Your device tree functions in
of_device.c,of_platform.c,prom.candprom_parse.care basically copies of the powerpc versions. This duplication is not helpful, better merge that code into new files indrivers/of/so that it can be shared.
These files are almost the same. There is small differences between them. I would like to avoid to merge this code with PowerPC because this generate a lot of mails in this steps.
BTW: OF code in powerpc have coding style violation.
Guys from PowerPC. Can you move these files around OF to drivers/of folder? or Can you propose easier way for me?
I think we can solve these files when we merge Microblaze to PowerPC branch.
Quoted 1 line
* The semaphore implementation will be obsolete in 2.6.26
I don't know. Which cpu has correct implemetnation?
Quoted 3 lines
* The
EXPORT_SYMBOLdefinitions forcsum_partialetc should be inarch/microblaze/lib/checksum.c, not inmicroblaze_ksyms.c, same for memcpy/memmove/memset.
OK. I fixed it.
Quoted 4 lines
* The platform directory is noticably empty. You can probably judge better how much platform specific code there will be in the future, but I would suspect that you're better off with a flat platform directory instead of subdirectories below that.
I consult this with John Williams and this was result of our meeting. This structure is more comfortable for adding new platform inside distribution. I would like to keep this for now. We'll see if is good or not in future.
Quoted 3 lines
* the
consistent.cimplementation 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/EnablingUncachedShadow
JW. Can you comment this?
Quoted 2 lines
* Your
dma_mapping.hdoesBUG()for almost everything. I suspect you could easily replace it with a trivial implementation, like thex86_32one.
OK. I'll synchronize this.
Quoted 4 lines
* I'm not sure if you really need something as sophisticated as the lmb code, if you don't have a real firmware, or even an MMU.
setup_memorycan probably work with something much simpler, and for theprom.cstuff, you may get away with #defining them tobootmem_allocetc.
LMB code cames with OF. You wrote that prom.c files and others are written for PowerPC and PowerPC uses lmb allocation. For me was simplier to add LMB code to Microblaze. As I wrote above. Microblaze have static (old configuration style) implementation for MMU. I think it will be improvident to redesign this code when I know that I will merge noMMU kernel with MMU.
Quoted 2 lines
* You don't seem to have any code for PCI, so the
pci.handpci-bridge.hfiles 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?
Quoted 7 lines
* The following files:
atomic.hchecksum.hio.hioctl.hioctls.hipcbuf.hmsgbuf.hparam.hpoll.hposix_types.hsembuf.hshmbuf.hshmparam.hsigcontext.hsignal.hsocket.hsockios.hstat.htermbits.htermios.htypes.hucontext.hall look like verbatim copies of some other architecture. Please do the next person to come up with a new architecture a favor and stick them ininclude/asm-genericinstead, including them from your own headers.
I'll look which files are the same with others arch.
Quoted 2 lines
* You
unistd.hcontains _syscall* macros. These were removed some time ago from all other architectures.
I removed it.
Quoted 2 lines
* You define a lot of
__ARCH_WANT_SYS_macros. Generally, these are for the syscalls you don't want.
ARCH_WANT is defined for syscalls which I don't want. I don't understand this.
I think that I ARCH_WANT is for syscalls which I want and IGNORE for rest. Am I right?
Quoted 2 lines
* You are missing a
include/asm-microblaze/Kbuildfile that lists all the header files you want to export to user space.
I add it. This files comes from PowerPC.
Quoted 1 line
Arnd <><
Thanks for your review,
Michal Simek
www.monstr.eu
Quoted 9 lines · Michal Simek
Quoted 4 lines
* Your device tree functions in
of_device.c,of_platform.c,prom.candprom_parse.care basically copies of the powerpc versions. This duplication is not helpful, better merge that code into new files indrivers/of/so that it can be shared.These files are almost the same. There is small differences between them. I would like to avoid to merge this code with PowerPC because this generate a lot of mails in this steps.
Quoted 6 lines
BTW: OF code in powerpc have coding style violation.
Guys from PowerPC. Can you move these files around OF to
drivers/offolder? or Can you propose easier way for me?I think we can solve these files when we merge Microblaze to PowerPC branch.
I think the easiest way is to include those patches in your series and ask for an Acked-by from paulus.
The order of the patches should be:
1. fix up any coding style issues you have found
2. move the files without further changes to drivers/of
3. add whatever code you need to make it work on both architectures
Be careful not to break sparc in the process, as they are already sharing substantial parts of the OF code with powerpc.
Quoted 3 lines
Quoted 1 line
* The semaphore implementation will be obsolete in 2.6.26
I don't know. Which cpu has correct implemetnation?
2.6.26 will have a common implementation in kernel/semaphore.c. All you need is a one-line asm/semaphore.h to #include linux/semaphore.h.
Quoted 11 lines
Quoted 3 lines
* the
consistent.cimplementation 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_shadowsstuff.
http://developer.petalogix.com/wiki/UserGuide/AdvancedTopics/EnablingUncachedShadow
JW. Can you comment this?From what I can see, your
consistent.ccode is just wrong and uses an
obsolete interface. Since you currently don't use it, I'd suggest to drop it from your current tree for the merge. We can discuss it again when you add MMU support.
Quoted 10 lines
Quoted 4 lines
* I'm not sure if you really need something as sophisticated as the lmb code, if you don't have a real firmware, or even an MMU.
setup_memorycan probably work with something much simpler, and for theprom.cstuff, you may get away with #defining them tobootmem_allocetc.LMB code cames with OF. You wrote that
prom.cfiles and others are written for PowerPC and PowerPC uses lmb allocation. For me was simplier to add LMB code to Microblaze. As I wrote above. Microblaze have static (old configuration style) implementation for MMU. I think it will be improvident to redesign this code when I know that I will merge noMMU kernel with MMU.
LMB doesn't have much to do with an MMU, but more with the way certain IBM machines extend the OF interfaces.
I'd recommend splitting prom.c into code that can be shared between powerpc and microblaze and architecture specific code. Anything that deals with LMB should go into powerpc, and you can simply use the alloc_bootmem mechanism for your architecture.
Quoted 9 lines
Quoted 7 lines
* The following files:
atomic.hchecksum.hio.hioctl.hioctls.hipcbuf.hmsgbuf.hparam.hpoll.hposix_types.hsembuf.hshmbuf.hshmparam.hsigcontext.hsignal.hsocket.hsockios.hstat.htermbits.htermios.htypes.hucontext.hall look like verbatim copies of some other architecture. Please do the next person to come up with a new architecture a favor and stick them ininclude/asm-genericinstead, including them from your own headers.I'll look which files are the same with others arch.
That was not my point, although it would be a good idea as well. The important bit is that your version of these files don't contain any architecture specific code (no guarantees, my review may have been sloppy). Even if every architecture so far has a different version of them, but any of them would be ok for you, please throw one of them into asm-generic and start using it.
All future architectures can simply use that copy as well, as long as they have the same constraints (e.g. you atomic.h assumes there are no atomic operations other than spinlock, iirc).
If you want to be really nice, look for the most common implementation across the existing architectures and put that into asm-generic. Also, please cc the linux-arch mailing list on any patch that adds a file in asm-generic.
Quoted 7 lines
Quoted 2 lines
* You define a lot of
__ARCH_WANT_SYS_macros. Generally, these are for the syscalls you don't want.
ARCH_WANTis defined for syscalls which I don't want. I don't understand this.I think that I
ARCH_WANTis for syscalls which I want and IGNORE for rest. Am I right?
Sorry, my comment was impossible to understand ;-).
What I meant is that a new architecture should not define these macros, because only architectures with a need for backwards compatibility want the syscalls they enable. If you find an exception and think you need one of them, please tell us.
Arnd <><
Quoted 5 lines · Arnd Bergmann
I'd recommend splitting
prom.cinto code that can be shared between powerpc and microblaze and architecture specific code. Anything that deals with LMB should go into powerpc, and you can simply use thealloc_bootmemmechanism for your architecture.
That is non trivial... the unflatten DT code among others relies heavily on the LMB's to allocate the objects.
We could split the early accessors, unflatten code, and kernel-side accessors at one point, though we already did most of it no ?
Ben.
Hi Ben,
Quoted 7 lines
Quoted 4 lines
I'd recommend splitting
prom.cinto code that can be shared between powerpc and microblaze and architecture specific code. Anything that deals with LMB should go into powerpc, and you can simply use thealloc_bootmemmechanism for your architecture.That is non trivial... the unflatten DT code among others relies heavily on the LMB's to allocate the objects.
I think so. Sharing code among archs looks nice and this way is definitely right. But starting with communication with PowerPC guys that this code I want to use in case that this code is not in vanilla. This is not good start for doing this.
I think if Microblaze will be in vanilla we can talked about separation MB and PPC part to kernel folder and shared code move to shared folder.
Quoted 2 lines
We could split the early accessors, unflatten code, and kernel-side accessors at one point, though we already did most of it no ?
Yes
Michal Simek
www.monstr.eu
Quoted 4 lines · Michal Simek
I think so. Sharing code among archs looks nice and this way is definitely right. But starting with communication with PowerPC guys that this code I want to use in case that this code is not in vanilla. This is not good start for doing this.
I have a commit queued up that moves lmb.c into the top-level lib directory so other architectures can use it easily. Dave Miller wanted this so he could use it for sparc64. That will go into Linus' tree when the merge window opens and will be in 2.6.26. So I don't see any reason why microblaze couldn't use the LMB stuff.
Paul.
Quoted 7 lines · Paul Mackerras
Quoted 4 lines · Michal Simek
I think so. Sharing code among archs looks nice and this way is definitely right. But starting with communication with PowerPC guys that this code I want to use in case that this code is not in vanilla. This is not good start for doing this.
Quoted 6 lines
I have a commit queued up that moves
lmb.cinto the top-level lib directory so other architectures can use it easily. Dave Miller wanted this so he could use it for sparc64. That will go into Linus' tree when the merge window opens and will be in 2.6.26. So I don't see any reason why microblaze couldn't use the LMB stuff.
Right, fair enough. I was mostly objecting to the idea of creating another copy of the lmb code when bootmem should be sufficient for what microblaze needs. Using the code from lib/lmb.c sounds fair enough when it's already there.
One more reason for the microblaze kernel to base on top of linux-next instead of mainline.
Arnd <><
Quoted 11 lines
Quoted 10 lines
Quoted 4 lines
I think so. Sharing code among archs looks nice and this way is definitely right. But starting with communication with PowerPC guys that this code I want to use in case that this code is not in vanilla. This is not good start for doing this.
I have a commit queued up that moves
lmb.cinto the top-level lib directory so other architectures can use it easily. Dave Miller wanted this so he could use it for sparc64. That will go into Linus' tree when the merge window opens and will be in 2.6.26. So I don't see any reason why microblaze couldn't use the LMB stuff.
Quoted 7 lines
Right, fair enough. I was mostly objecting to the idea of creating another copy of the lmb code when bootmem should be sufficient for what microblaze needs. Using the code from
lib/lmb.csounds fair enough when it's already there.One more reason for the microblaze kernel to base on top of linux-next instead of mainline.
For me is not difficult to use lmb from microblaze/mm or from lib if the files are the same.
Michal Simek
Quoted 6 lines · Michal Simek
Quoted 2 lines
One more reason for the microblaze kernel to base on top of linux-next instead of mainline.
For me is not difficult to use lmb from microblaze/mm or from lib if the files are the same.
What I meant is that there are a number of reasons to use linux-next as a base for your kernel (this being one of them) and few against.
Arnd <><
Hi all,
I update Microblaze kernel to latest Linus tree. I fixed some problems which come with it.
Regards,
Michal
Quoted 12 lines
Quoted 5 lines
Quoted 2 lines
One more reason for the microblaze kernel to base on top of linux-next instead of mainline.
For me is not difficult to use lmb from microblaze/mm or from lib if the files are the same.
What I meant is that there are a number of reasons to use linux-next as a base for your kernel (this being one of them) and few against.
Arnd <><
Hi Michal
Le mercredi 23 avril 2008, Michal Simek a écrit :
Quoted 4 lines
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.
If this represents too much work for you, we can probably add it later.
Great work !
Quoted 6 lines · Florian Fainelli
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.
If this represents too much work for you, we can probably add it later.
The problem as far as I can see is that the existing header files just don't work without a platform implementation.
I think it would be less confusing to leave them out. If you need PCI, it's probably easier to add new files for these and get them working at the same time.
Arnd <><
Hi,
I am decided to remove content pci.h and pci-bridge.h. It is easier for me now. This step comes soon. I gonna change consistent.c file with use it.
The files will be in asm folder because OF point to them but the files will be empty or almost empty.
Regards,
Michal Simek
Quoted 17 lines
Quoted 6 lines
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.
If this represents too much work for you, we can probably add it later.
The problem as far as I can see is that the existing header files just don't work without a platform implementation.
I think it would be less confusing to leave them out. If you need PCI, it's probably easier to add new files for these and get them working at the same time.
Arnd <><
Quoted 10 lines
Hi Michal
Quoted 4 lines
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.
Quoted 1 line
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.
Quoted 1 line
Great work !
Have a good day,
Michal Simek
Hi,
Quoted 11 lines · Michal Simek
Quoted 10 lines
Hi Michal
Quoted 4 lines
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.
Quoted 8 lines
I'll add PCI parts as I will have a reason to do it. I have no PCI devices connected to MB now.
Quoted 1 line
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.
Quoted 1 line
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
Quoted 3 lines
Have a good day,
Michal Simek
Signature · 3 lines
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
Hi Paul,
Quoted 6 lines
Quoted 5 lines
I think so. Sharing code among archs looks nice and this way is definitely right. But starting with communication with PowerPC guys that this code I want to use in case that this code is not in vanilla. This is not good start for doing this.
Quoted 7 lines
I have a commit queued up that moves
lmb.cinto the top-level lib directory so other architectures can use it easily. Dave Miller wanted this so he could use it for sparc64. That will go into Linus' tree when the merge window opens and will be in 2.6.26. So I don't see any reason why microblaze couldn't use the LMB stuff.Paul.
I will test it.
Thanks Paul,
Michal Simek
Quoted 10 lines · Michal Simek
Hi Ben,
Quoted 7 lines
Quoted 4 lines
I'd recommend splitting
prom.cinto code that can be shared between powerpc and microblaze and architecture specific code. Anything that deals with LMB should go into powerpc, and you can simply use thealloc_bootmemmechanism for your architecture.That is non trivial... the unflatten DT code among others relies heavily on the LMB's to allocate the objects.
Quoted 6 lines
I think so. Sharing code among archs looks nice and this way is definitely right. But starting with communication with PowerPC guys that this code I want to use in case that this code is not in vanilla. This is not good start for doing this.
I think if Microblaze will be in vanilla we can talked about separation MB and PPC part to kernel folder and shared code move to shared folder.
Well, LMB code is moving to generic anyway... So we may as well move more stuff there ;-)
Cheers,
Ben.
Hi,
Quoted 5 lines
Quoted 4 lines
I'd recommend splitting
prom.cinto code that can be shared between powerpc and microblaze and architecture specific code. Anything that deals with LMB should go into powerpc, and you can simply use thealloc_bootmemmechanism for your architecture.
Quoted 7 lines
That is non trivial... the unflatten DT code among others relies heavily on the LMB's to allocate the objects.
We could split the early accessors, unflatten code, and kernel-side accessors at one point, though we already did most of it no ?
Ben.
I look at latest LMB version currenty in lib folder. There is some changes which I think go against version.
I would like to ask some question about.
in include/asm-powerpc/lmb.h is written LMB_REAL_LIMIT.
Is this real limit memory limit? Why I ask. I think powerpc start with main memory from zero address and you can set your high limit from zero. In this case is high limit equal to size of memory.
In Microblaze systems we don't have main memory from zero. Starting point can be everywhere in 2^32.
I hope I can avoid in this constant in MB system and only direct start and size mem with DTS description. Am I right?
The similar code was added to of files which are in arch/powerpc/kernel/ folder. I would like to fix LMB and OF together.
I have some fixed around coding style violation. I'll send them ASAP.
I don't have any idea what files use Sparc. Can you inform me about? I don't want to break something with MB port.
Thanks for info.
Regards,
Michal Simek
Hi all
Quoted 5 lines
Quoted 2 lines
Quoted 1 line
* The semaphore implementation will be obsolete in 2.6.26
I don't know. Which cpu has correct implemetnation?
2.6.26 will have a common implementation in
kernel/semaphore.c. All you need is a one-lineasm/semaphore.hto #includelinux/semaphore.h.
I fixed this issue.
Regards,
Michal Simek
Quoted 4 lines
Quoted 4 lines
* the
consistent.cimplementation looks strange. Is any of that code even used anywhere? What is it good for, considering that you don't
have
Quoted 3 lines
Quoted 1 line
an mmu?
We have prepared MMU code. I hope that this code for FDT kernel comes
soon.
Quoted 1 line
This code is written by John Williams. I have never changed it. I see
that this
Quoted 2 lines
code solves problems around
ucached_shadowsstuff.
http://developer.petalogix.com/wiki/UserGuide/AdvancedTopics/EnablingUnc
achedShadow
Quoted 1 line
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.
Quoted 1 line
Quoted 1 line
* Your
dma_mapping.hdoesBUG()for almost everything. I suspect you
could
Quoted 1 line
Quoted 1 line
easily replace it with a trivial implementation, like the
x86_32
one.
Quoted 2 lines
OK. I'll synchronize this.
This is also in git.xilinx.com.
Quoted 1 line
Quoted 1 line
* You don't seem to have any code for PCI, so the
pci.hand
pci-bridge.h
Quoted 3 lines
Quoted 1 line
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
Quoted 1 line
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.
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.
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.
Steve
Hi Steve
Quoted 10 lines
Quoted 2 lines
Quoted 2 lines
* the
consistent.cimplementation looks strange. Is any of that code even used anywhere? What is it good for, considering that you don'thave
Quoted 2 lines
Quoted 1 line
an mmu?
We have prepared MMU code. I hope that this code for FDT kernel comes
soon.
Quoted 1 line
This code is written by John Williams. I have never changed it. I see
that this
Quoted 2 lines
code solves problems around
ucached_shadowsstuff.
Quoted 8 lines
http://developer.petalogix.com/wiki/UserGuide/AdvancedTopics/EnablingUnc
achedShadowQuoted 1 line
JW. Can you comment this?
It probably makes sense to grab:
arch/microblaze/mm/dma-coherent.cfrom git.xilinx.com and dropconsistent.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.
Quoted 7 lines
Quoted 1 line
Quoted 1 line
* Your
dma_mapping.hdoesBUG()for almost everything. I suspect youcould
Quoted 1 line
Quoted 1 line
easily replace it with a trivial implementation, like the
x86_32one.
Quoted 1 line
OK. I'll synchronize this.
This is also in git.xilinx.com.
ok.
Quoted 9 lines
Quoted 1 line
Quoted 1 line
* You don't seem to have any code for PCI, so the
pci.hand
pci-bridge.hQuoted 2 lines
Quoted 1 line
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
Quoted 1 line
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
Quoted 5 lines
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.
Quoted 2 lines
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
Hi Arnd,
Quoted 10 lines
Quoted 4 lines
I would like to ask you for review all microblaze code especially
arch/microblazeandinclude/asm-microblaze. Please don't send me question to drivers - Microblaze will use only uartlite driver (only add on or toKconfig- that's enough for now).I'm certainly willing to help review it, but I think the timing is too short for asking for a 2.6.26 merge. Judging from experience, a new architecture review takes a few weeks to sort out all the issues you want resolved before merging, so posting them now would put you in a much more comfortable position when targeting a 2.6.27 merge.
Thanks for your help. I know that the time is short.:-( We'll see. I will request for merge if I know Microblaze cpu is clean.
Quoted 6 lines
One of the things I always wanted to have is a common location for all the things that get duplicated verbatim into each new architecture, like all the
include/asm/{fcntl,ioctls,ipcbuf,mman,poll,posix_types,sem_buf}.hand others that define part of the syscall ABI.Arnd <><
Include files are pain I know.
Michal Simek
www.monstr.eu