Toshiba JMR 3927 working setup?
Hi,
I have a JMR3927 based system and I got it to work with the 2.6.23.14 kernel, but used 0xff0000 instead of 0xff000. The offset passed in was 0xfffec000 which isn't within the 0xff000000 - 0xff0ff000.
Max
Subject: [MIPS] Fix plat_ioremap for JMR3927
TX39XX's "reserved" segment in CKSEG3 area is 0xff000000-0xfffeffff.
Signed-off-by: Atsushi Nemoto <[email protected]> --- diff --git a/include/asm-mips/mach-jmr3927/ioremap.h b/include/asm-mips/mach-jmr3927/ioremap.h index aa131ad..ac3be35 100644 --- a/include/asm-mips/mach-jmr3927/ioremap.h +++ b/include/asm-mips/mach-jmr3927/ioremap.h @@ -25,7 +25,7 @@ static inline void __iomem *plat_ioremap(phys_t offset, unsigned long size, { #define TXX9_DIRECTMAP_BASE 0xff000000ul if (offset >= TXX9_DIRECTMAP_BASE && - offset < TXX9_DIRECTMAP_BASE + 0xf0000) + offset < TXX9_DIRECTMAP_BASE + 0xff000) return (void __iomem *)offset; return NULL; }
Quoted 3 lines · Max Okumoto
I have a JMR3927 based system and I got it to work with the 2.6.23.14 kernel, but used
0xff0000instead of0xff000. The offset passed in was0xfffec000which isn't within the0xff000000-0xff0ff000.
Thank you for good news. (and excuse my double fault...)
Ralf, please apply this to 2.6.23-stable and 2.6.24-stable.
Subject: [MIPS] Fix plat_ioremap for JMR3927 (take 2)
TX39XX's "reserved" segment in CKSEG3 area is 0xff000000-0xfffeffff.
---
include/asm-mips/mach-jmr3927/ioremap.h +1 -1
@@ -25,7 +25,7 @@ static inline void __iomem *plat_ioremap(phys_t offset, unsigned long size, {#define TXX9_DIRECTMAP_BASE 0xff000000ulif (offset >=TXX9_DIRECTMAP_BASE && - offset <TXX9_DIRECTMAP_BASE +0xf0000 ) + offset <TXX9_DIRECTMAP_BASE +0xff0000 )return (void __iomem *)offset;return NULL ; }
Quoted 11 lines · Atsushi Nemoto
Quoted 4 lines · Max Okumoto
I have a JMR3927 based system and I got it to work with the 2.6.23.14 kernel, but used
0xff0000instead of0xff000. The offset passed in was0xfffec000which isn't within the0xff000000-0xff0ff000.Thank you for good news. (and excuse my double fault...)
Ralf, please apply this to 2.6.23-stable and 2.6.24-stable.
The change does appear to work for me also, however, I still see no kernel messages at all. The only way that I can get any output is via puts() and prom_putchar() (the latter I put into emit_log_char(char c) of printk.c).
I have not gotten past the root mounting stage because I have not attached an image yet, which I will try as soon as I get some time again.
Thanks for your help
Quoted 4 lines · Gregor Waltz
The change does appear to work for me also, however, I still see no kernel messages at all. The only way that I can get any output is via
puts()andprom_putchar()(the latter I put intoemit_log_char(char c)ofprintk.c).
If you were using ttyS1, did you try CONFIG_SERIAL_TXX9_STDSERIAL=y ?
Also, as http://www.linux-mips.org/wiki/JMR-TX3927 said, PCI support is broken...
---
Atsushi Nemoto
Ralf Baechle
AppliedQuoted 9 lines · Atsushi Nemoto
Quoted 3 lines · Max Okumoto
I have a JMR3927 based system and I got it to work with the 2.6.23.14 kernel, but used
0xff0000instead of0xff000. The offset passed in was0xfffec000which isn't within the0xff000000-0xff0ff000.Thank you for good news. (and excuse my double fault...)
Ralf, please apply this to 2.6.23-stable and 2.6.24-stable.
Applied. Thanks,
Ralf