* Re: [PATCH] i2c-mpc: Add support for 64bit system
From: Ben Dooks @ 2011-03-15 16:12 UTC (permalink / raw)
To: Kumar Gala; +Cc: linuxppc-dev, linux-i2c, ben-linux, B33228
In-Reply-To: <1300204963-15855-1-git-send-email-galak@kernel.crashing.org>
On Tue, Mar 15, 2011 at 11:02:43AM -0500, Kumar Gala wrote:
> Currently i2c-mpc supports 32bit system only, this modification makes it
> supported on both 32-bit and 64-bit systems. The P5020 is the first
> 64-bit PPC system with the i2c-mpc controller.
>
> Based in patch from Xulei <B33228@freescale.com>
>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
ok, will add to -next
> ---
> drivers/i2c/busses/Kconfig | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
> index 113505a..107d5c2 100644
> --- a/drivers/i2c/busses/Kconfig
> +++ b/drivers/i2c/busses/Kconfig
> @@ -433,7 +433,7 @@ config I2C_IXP2000
>
> config I2C_MPC
> tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
> - depends on PPC32
> + depends on PPC
> help
> If you say yes to this option, support will be included for the
> built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
> --
> 1.7.2.3
>
--
Ben Dooks, ben@fluff.org, http://www.fluff.org/ben/
Large Hadron Colada: A large Pina Colada that makes the universe disappear.
^ permalink raw reply
* Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
From: nello martuscielli @ 2011-03-15 16:44 UTC (permalink / raw)
Cc: linuxppc-dev, acrux @ cruxppc
In-Reply-To: <AANLkTinOo9tJ5=WWF2WJEZn3VwAUOa+SOYE0txNm-moM@mail.gmail.com>
ok, it seems that no one is interested to fix Pegasos1 G3 600MHz support.
But if someone is capable (i don't have this skill) here what it
happens reading from serial debug console untill it freezes with
linux-2.6.36.4
Pegasos Boot Strap (c) 2002 bplan GmbH
Running on CPU PVR:00083311
PLL setting : 00000001
Enable L1 ICache... Done.
Setting ROM Defaults... Done.
Configuring SDRAM...
08000000
10000000
Delaying...Done.
RAMSIZE = 18000000
00000004
Reading W83194 : 00FFFFFFFFFF0000 Done.
Setting Front Side Bus to 100MHz... Done.
Releasing IDE reset ... Done.
Configuring Legacy Devices
Initializing KBD... Done.
PLL setting : 00000003
10000000
Done.
FFFFFFFF
BIOS: Stage 2 entered arg(FFFC0000,00000000,18000000)
BIOS: MachineInfo at 0FFFFE68
BIOS: set MemPool limit to BAT size (old=18000000 new=10000000)
BIOS: 0F6FFFE8 bytes added to mempool
LoadFromRFS: starting
LoadFromRFS: lib module 00 has abs load adr at 00C00000
CopyModule: start
CopyModule: load address : 00C00000
CopyModule: copy module to ram...done
ModuleCopy: expanding... done
LoadFromRFS: 00000001 modules out of 00000001 loaded
InitLib: start
InitLib: call module as OF
allocated g_e=0xFD00008 (len=19232)
install_root: pkg=0xFD53B90
after init_environ e=0xFD00008
running nvramrc...
after running nvramrc
no/bad nvramrc - performing default startup script
Bus addresses:
253@2
I/O addresses:
7936@FE002100
Memory addresses:
127M@88040000
1.3G@98000000
Prefetchable memory addresses:
install_ata_disk_driver: reg=0x1000
init_drive: reset controller 0x1000/0x100E
init_drive: allow 4-bits for heads
init_drive: select drive 0
init_drive: seccnt=0x1 sector=0x1 cyl_lo=0x0 cyl_hi=0x0
init_drive: error=0x1 status=0x50 status2=0x50
init_drive: identify drive: atapi=0
install_ata_disk_driver: return no error (0)
install_ata_disk_driver: reg=0x1000
init_drive: allow 4-bits for heads
init_drive: select drive 1
init_drive: seccnt=0x1 sector=0x1 cyl_lo=0x14 cyl_hi=0xEB
init_drive: error=0x1 status=0x0 status2=0x0
init_drive: identify drive: atapi=1
atapi_cmd: cmdlen=12
atapi_cmd: inlen=8 len=65534
install_ata_disk_driver: return no error (0)
install_ata_disk_driver: reg=0x1010
init_drive: reset controller 0x1010/0x101E
init_drive: allow 4-bits for heads
init_drive: select drive 0
init_drive: seccnt=0x20 sector=0x20 cyl_lo=0x20 cyl_hi=0x20
init_drive: error=0x20 status=0x20 status2=0x20
ATA-wait-ready: timeout: status=0x20
init_drive: failed
install_ata_disk_driver: reg=0x1010
init_drive: allow 4-bits for heads
init_drive: select drive 1
init_drive: seccnt=0x30 sector=0x30 cyl_lo=0x30 cyl_hi=0x30
init_drive: error=0x30 status=0x30 status2=0x30
ATA-wait-ready: timeout: status=0x30
init_drive: failed
Bus addresses:
254@2
I/O addresses:
8@FE001038
3072@FE001400
48K@FE004000
Memory addresses:
1792@A0000100
1.2G@A0001000
Prefetchable memory addresses:
12M@FD400000
F_INSTALL_CONSOLE: BEGIN
F_INSTALL_CONSOLE: ALIASING SCREEN
F_INSTALL_CONSOLE: ALIASING KBD
EMULATION INT HANDLER ENTERED WITH:
INT NO: 15
EAX=0003 EBX=1111 ECX=2222 EDX=3333 ESP=0000 EBP=5555 ESI=6666 EDI=7777
AX=4E08 BX=C505 CX=0003 DX=202A SP=6CAA BP=5555 SI=5CF9 DI=7777
DS=C000 ES=BAD0 SS=C000 CS=F000 IP=FE15 NV UP -- PL ZR NA PE NC
CS:IP = F4 C558 C000 0244 3000 0000 01B4 AC63 0200
UNHANDLED INT 10 FUNCTION 0007 WITHIN EMULATION
F_INSTALL_CONSOLE: END
auto-booting...
do_load: dev="" dlen=0 args="" alen=0
do_load: alstr=""
do_load: path doesn't start with /
do_load: <diag-device> == <eth>
do_load: no args..use the default
do_load: <diag-file> == <diag>
try_load: dev="eth" dlen=3 args="diag" alen=4
entering main read/eval loop...
[...]
atapi_cmd: cmdlen=12
atapi_cmd: inlen=2048 len=2048
iso_walk: read: name="zImage.chrp" extent=0x44FD size=0x337272 ret=no error
iso9660: return R_END
file_system: return end (-4089)
disk-label return len=3371634 ret=end (-4089)
ata_disk_close
disk-label close:
checking exec type Fcode
fcode_is_exec: load=0x400000 loadlen=3371634
checking exec type Forth
checking exec type ELF
f_go:
checking exec type Fcode
fcode_is_exec: load=0x400000 loadlen=3371634
checking exec type Forth
checking exec type ELF
alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914
alloc_constrained: min 0x0, max 0xFFFFFFFF, align 0x1000, mask
0xFFFFFFFF, size 0x332000, addr 0x300000
alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1
0xFD54910 u2 0xFD54914 u3 0xFD54918
alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x300000
size 0xFD00000
alloc_constrained: fsblock 0x0
alloc_constrained: addr[] 0x300000
alloc_constrained: bsize[] 0xFD00000
alloc_constrained: passed min check
alloc_constrained: addr 0x300000, align 0xFFF, off 0x69696969
sum 0x0
alloc_constrained: passed align check
alloc_constrained: passed max check
alloc_constrained: passed mask check
alloc_constrained: passed full size check
alloc_constrained: passed size check
alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914
alloc_constrained: min 0x0, max 0xFFFFFFFF, align 0x1000, mask
0xFFFFFFFF, size 0x6883C0, addr 0x632000
alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1
0xFD54910 u2 0xFD54914 u3 0xFD54918
alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x632000
size 0xF9CE000
alloc_constrained: fsblock 0x0
alloc_constrained: addr[] 0x632000
alloc_constrained: bsize[] 0xF9CE000
alloc_constrained: passed min check
alloc_constrained: addr 0x632000, align 0xFFF, off 0x0
sum 0x0
alloc_constrained: passed align check
alloc_constrained: passed max check
alloc_constrained: passed mask check
alloc_constrained: passed full size check
alloc_constrained: passed size check
and here giving a try with a smaller (1.9MB) linux boot kernel
[...]
atapi_cmd: cmdlen=12
atapi_cmd: inlen=2048 len=2048
iso_walk: read: name="zImage.chrp" extent=0x3CC size=0x1D8A1A ret=no error
iso9660: return R_END
file_system: return end (-4089)
disk-label return len=1935898 ret=end (-4089)
ata_disk_close
disk-label close:
checking exec type Fcode
fcode_is_exec: load=0x400000 loadlen=1935898
checking exec type Forth
checking exec type ELF
f_go:
checking exec type Fcode
fcode_is_exec: load=0x400000 loadlen=1935898
checking exec type Forth
checking exec type ELF
alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914
alloc_constrained: min 0x0, max 0xFFFFFFFF, align 0x1000, mask
0xFFFFFFFF, size 0x1D3000, addr 0x300000
alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1
0xFD54910 u2 0xFD54914 u3 0xFD54918
alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x300000
size 0xFD00000
alloc_constrained: fsblock 0x0
alloc_constrained: addr[] 0x300000
alloc_constrained: bsize[] 0xFD00000
alloc_constrained: passed min check
alloc_constrained: addr 0x300000, align 0xFFF, off 0x69696969
sum 0x0
alloc_constrained: passed align check
alloc_constrained: passed max check
alloc_constrained: passed mask check
alloc_constrained: passed full size check
alloc_constrained: passed size check
alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914
alloc_constrained: min 0x0, max 0xFFFFFFFF, align 0x1000, mask
0xFFFFFFFF, size 0x3AC9A0, addr 0x4D3000
alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1
0xFD54910 u2 0xFD54914 u3 0xFD54918
alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x4D3000
size 0xFB2D000
alloc_constrained: fsblock 0x0
alloc_constrained: addr[] 0x4D3000
alloc_constrained: bsize[] 0xFB2D000
alloc_constrained: passed min check
alloc_constrained: addr 0x4D3000, align 0xFFF, off 0x0
sum 0x0
alloc_constrained: passed align check
alloc_constrained: passed max check
alloc_constrained: passed mask check
alloc_constrained: passed full size check
alloc_constrained: passed size check
^ permalink raw reply
* Re: [PATCH 1/2] kdump: Allow shrinking of kdump region to be overridden
From: Mahesh J Salgaonkar @ 2011-03-15 16:52 UTC (permalink / raw)
To: Américo Wang
Cc: kexec, linux-kernel, linuxppc-dev, Anton Blanchard, akpm,
Eric W. Biederman
In-Reply-To: <AANLkTi=aDzCaa7_=5XTrnJCzmZPrDy3omXwDarEF8XmH@mail.gmail.com>
On Tue, Mar 15, 2011 at 03:52:38PM +0800, Américo Wang wrote:
> On Tue, Mar 15, 2011 at 2:13 AM, Mahesh J Salgaonkar
> <mahesh@linux.vnet.ibm.com> wrote:
> >
> > During free we do free all of them including RMO region. But since the rtas
> > region is always on top of RMO, crashkernel memory overlaps rtas region and
> > we endup freeing that even, which is causing the crash.
> >
>
> Okay, but with this patch applied, we will just ignore rtas region, right?
Correct.
> Thus, when I echo 0 to free all the 128M crashkernel memory, the final
> result will be 32M left, which means crash_size will still show 32M.
> This looks odd.
>
> How about skipping the 32M as a whole? I mean once the region being freed
> has overlap with this rtas region, skip the whole rtas region, and let
> crash_size
> show 0?
The existing code from crash_shrink_memory() function reduces the crash
size to 0 when echo'ed 0. I did test this patchset and verified that
/sys/kernel/kexec_crash_size show 0 value.
Thanks,
-Mahesh.
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
--
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
^ permalink raw reply
* Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
From: Baurzhan Ismagulov @ 2011-03-15 16:54 UTC (permalink / raw)
To: linuxppc-dev
In-Reply-To: <AANLkTim6urK-1-0MXrXZPTDWifZsi+7QEH_c8S-vzWSL@mail.gmail.com>
On Tue, Mar 15, 2011 at 05:44:49PM +0100, nello martuscielli wrote:
> But if someone is capable (i don't have this skill) here what it
> happens reading from serial debug console untill it freezes with
> linux-2.6.36.4
What is the last kernel version working on that machine? If you have a
working kernel and can build kernels, you could try bisecting to
identify the change that led to that. Perhaps then someone could have
some ideas.
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
^ permalink raw reply
* Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
From: Gerhard Pircher @ 2011-03-15 17:14 UTC (permalink / raw)
To: nello martuscielli; +Cc: linuxppc-dev, acrux_it
In-Reply-To: <AANLkTim6urK-1-0MXrXZPTDWifZsi+7QEH_c8S-vzWSL@mail.gmail.com>
-------- Original-Nachricht --------
> Datum: Tue, 15 Mar 2011 17:44:49 +0100
> Von: nello martuscielli <ppc.addon@gmail.com>
> An:
> CC: linuxppc-dev@lists.ozlabs.org, "acrux @ cruxppc" <acrux_it@libero.it>
> Betreff: Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
> ok, it seems that no one is interested to fix Pegasos1 G3 600MHz
> support.
>
> But if someone is capable (i don't have this skill) here what it
> happens reading from serial debug console untill it freezes with
> linux-2.6.36.4
>
> Pegasos Boot Strap (c) 2002 bplan GmbH
> Running on CPU PVR:00083311
> PLL setting : 00000001
> Enable L1 ICache...
> Done.
> Setting ROM Defaults...
> Done.
> Configuring SDRAM...
> 08000000
> 10000000
> Delaying...Done.
> RAMSIZE = 18000000
> 00000004
> Reading W83194 : 00FFFFFFFFFF0000
> Done.
> Setting Front Side Bus to 100MHz...
> Done.
> Releasing IDE reset ...
> Done.
> Configuring Legacy Devices
> Initializing KBD...
> Done.
> PLL setting : 00000003
> 10000000
> Done.
> FFFFFFFF
> BIOS: Stage 2 entered arg(FFFC0000,00000000,18000000)
> BIOS: MachineInfo at 0FFFFE68
> BIOS: set MemPool limit to BAT size (old=18000000 new=10000000)
> BIOS: 0F6FFFE8 bytes added to mempool
> LoadFromRFS: starting
> LoadFromRFS: lib module 00 has abs load adr at 00C00000
> CopyModule: start
> CopyModule: load address : 00C00000
> CopyModule: copy module to ram...done
> ModuleCopy: expanding... done
> LoadFromRFS: 00000001 modules out of 00000001 loaded
> InitLib: start
> InitLib: call module as OF
> allocated g_e=0xFD00008 (len=19232)
> install_root: pkg=0xFD53B90
> after init_environ e=0xFD00008
> running nvramrc...
> after running nvramrc
> no/bad nvramrc - performing default startup script
> Bus addresses:
> 253@2
> I/O addresses:
> 7936@FE002100
> Memory addresses:
> 127M@88040000
> 1.3G@98000000
> Prefetchable memory addresses:
> install_ata_disk_driver: reg=0x1000
> init_drive: reset controller 0x1000/0x100E
> init_drive: allow 4-bits for heads
> init_drive: select drive 0
> init_drive: seccnt=0x1 sector=0x1 cyl_lo=0x0 cyl_hi=0x0
> init_drive: error=0x1 status=0x50 status2=0x50
> init_drive: identify drive: atapi=0
> install_ata_disk_driver: return no error (0)
> install_ata_disk_driver: reg=0x1000
> init_drive: allow 4-bits for heads
> init_drive: select drive 1
> init_drive: seccnt=0x1 sector=0x1 cyl_lo=0x14 cyl_hi=0xEB
> init_drive: error=0x1 status=0x0 status2=0x0
> init_drive: identify drive: atapi=1
> atapi_cmd: cmdlen=12
> atapi_cmd: inlen=8 len=65534
> install_ata_disk_driver: return no error (0)
> install_ata_disk_driver: reg=0x1010
> init_drive: reset controller 0x1010/0x101E
> init_drive: allow 4-bits for heads
> init_drive: select drive 0
> init_drive: seccnt=0x20 sector=0x20 cyl_lo=0x20 cyl_hi=0x20
> init_drive: error=0x20 status=0x20 status2=0x20
> ATA-wait-ready: timeout: status=0x20
> init_drive: failed
> install_ata_disk_driver: reg=0x1010
> init_drive: allow 4-bits for heads
> init_drive: select drive 1
> init_drive: seccnt=0x30 sector=0x30 cyl_lo=0x30 cyl_hi=0x30
> init_drive: error=0x30 status=0x30 status2=0x30
> ATA-wait-ready: timeout: status=0x30
> init_drive: failed
> Bus addresses:
> 254@2
> I/O addresses:
> 8@FE001038
> 3072@FE001400
> 48K@FE004000
> Memory addresses:
> 1792@A0000100
> 1.2G@A0001000
> Prefetchable memory addresses:
> 12M@FD400000
> F_INSTALL_CONSOLE: BEGIN
> F_INSTALL_CONSOLE: ALIASING SCREEN
> F_INSTALL_CONSOLE: ALIASING KBD
> EMULATION INT HANDLER ENTERED WITH:
> INT NO: 15
>
> EAX=0003 EBX=1111 ECX=2222 EDX=3333 ESP=0000 EBP=5555 ESI=6666 EDI=7777
> AX=4E08 BX=C505 CX=0003 DX=202A SP=6CAA BP=5555 SI=5CF9 DI=7777
> DS=C000 ES=BAD0 SS=C000 CS=F000 IP=FE15 NV UP -- PL ZR NA PE NC
> CS:IP = F4 C558 C000 0244 3000 0000 01B4 AC63 0200
> UNHANDLED INT 10 FUNCTION 0007 WITHIN EMULATION
> F_INSTALL_CONSOLE: END
> auto-booting...
> do_load: dev="" dlen=0 args="" alen=0
> do_load: alstr=""
> do_load: path doesn't start with /
> do_load: <diag-device> == <eth>
> do_load: no args..use the default
> do_load: <diag-file> == <diag>
> try_load: dev="eth" dlen=3 args="diag" alen=4
> entering main read/eval loop...
>
> [...]
> atapi_cmd: cmdlen=12
> atapi_cmd: inlen=2048 len=2048
> iso_walk: read: name="zImage.chrp" extent=0x44FD size=0x337272 ret=no
> error
> iso9660: return R_END
> file_system: return end (-4089)
> disk-label return len=3371634 ret=end (-4089)
> ata_disk_close
> disk-label close:
> checking exec type Fcode
> fcode_is_exec: load=0x400000 loadlen=3371634
> checking exec type Forth
> checking exec type ELF
> f_go:
> checking exec type Fcode
> fcode_is_exec: load=0x400000 loadlen=3371634
> checking exec type Forth
> checking exec type ELF
> alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914
> alloc_constrained: min 0x0, max 0xFFFFFFFF, align 0x1000, mask
> 0xFFFFFFFF, size 0x332000, addr 0x300000
> alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1
> 0xFD54910 u2 0xFD54914 u3 0xFD54918
> alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x300000
> size 0xFD00000
> alloc_constrained: fsblock 0x0
> alloc_constrained: addr[] 0x300000
> alloc_constrained: bsize[] 0xFD00000
> alloc_constrained: passed min check
> alloc_constrained: addr 0x300000, align 0xFFF, off 0x69696969
> sum 0x0
> alloc_constrained: passed align check
> alloc_constrained: passed max check
> alloc_constrained: passed mask check
> alloc_constrained: passed full size check
> alloc_constrained: passed size check
> alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914
> alloc_constrained: min 0x0, max 0xFFFFFFFF, align 0x1000, mask
> 0xFFFFFFFF, size 0x6883C0, addr 0x632000
> alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1
> 0xFD54910 u2 0xFD54914 u3 0xFD54918
> alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x632000
> size 0xF9CE000
> alloc_constrained: fsblock 0x0
> alloc_constrained: addr[] 0x632000
> alloc_constrained: bsize[] 0xF9CE000
> alloc_constrained: passed min check
> alloc_constrained: addr 0x632000, align 0xFFF, off 0x0
> sum 0x0
> alloc_constrained: passed align check
> alloc_constrained: passed max check
> alloc_constrained: passed mask check
> alloc_constrained: passed full size check
> alloc_constrained: passed size check
>
>
>
> and here giving a try with a smaller (1.9MB) linux boot kernel
> [...]
> atapi_cmd: cmdlen=12
> atapi_cmd: inlen=2048 len=2048
> iso_walk: read: name="zImage.chrp" extent=0x3CC size=0x1D8A1A ret=no error
> iso9660: return R_END
> file_system: return end (-4089)
> disk-label return len=1935898 ret=end (-4089)
> ata_disk_close
> disk-label close:
> checking exec type Fcode
> fcode_is_exec: load=0x400000 loadlen=1935898
> checking exec type Forth
> checking exec type ELF
> f_go:
> checking exec type Fcode
> fcode_is_exec: load=0x400000 loadlen=1935898
> checking exec type Forth
> checking exec type ELF
> alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914
> alloc_constrained: min 0x0, max 0xFFFFFFFF, align 0x1000, mask
> 0xFFFFFFFF, size 0x1D3000, addr 0x300000
> alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1
> 0xFD54910 u2 0xFD54914 u3 0xFD54918
> alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x300000
> size 0xFD00000
> alloc_constrained: fsblock 0x0
> alloc_constrained: addr[] 0x300000
> alloc_constrained: bsize[] 0xFD00000
> alloc_constrained: passed min check
> alloc_constrained: addr 0x300000, align 0xFFF, off 0x69696969
> sum 0x0
> alloc_constrained: passed align check
> alloc_constrained: passed max check
> alloc_constrained: passed mask check
> alloc_constrained: passed full size check
> alloc_constrained: passed size check
> alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914
> alloc_constrained: min 0x0, max 0xFFFFFFFF, align 0x1000, mask
> 0xFFFFFFFF, size 0x3AC9A0, addr 0x4D3000
> alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1
> 0xFD54910 u2 0xFD54914 u3 0xFD54918
> alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x4D3000
> size 0xFB2D000
> alloc_constrained: fsblock 0x0
> alloc_constrained: addr[] 0x4D3000
> alloc_constrained: bsize[] 0xFB2D000
> alloc_constrained: passed min check
> alloc_constrained: addr 0x4D3000, align 0xFFF, off 0x0
> sum 0x0
> alloc_constrained: passed align check
> alloc_constrained: passed max check
> alloc_constrained: passed mask check
> alloc_constrained: passed full size check
> alloc_constrained: passed size check
I don't know much about the Pegasos OF, but did you give GRUB2 for OF
a try? Maybe it can boot a newer Linux kernel, if it is not a device
tree related problem.
On the other side you mentioned this workaround in
arch/ppc/kernel/prom_init.c to me some time ago:
unsigned long __init prom_init(int r3, int r4, prom_entry pp) :
> node = call_prom("finddevice", 1, 1, "/");
> rc = call_prom("getprop", 4, 1, node, "model", model, sizeof(model));
> if (rc > 0 && !strncmp (model, "Pegasos", 7)
> && strncmp (model, "Pegasos2", 8)) {
> /* Pegasos 1 has a broken translate method in the OF,
> * and furthermore the BATs are mapped 1:1 so the phys
> * address calculated above is correct, so let's use
> * it directly.
> */
> } else if (offset == 0) {
> /* If we are already running at 0xc0000000, we assume we were
> * loaded by an OF bootloader which did set a BAT for us.
> * This breaks OF translate so we force phys to be 0.
> */
> prom_print("(already at 0xc0000000) phys=0\n");
> phys = 0;
> } else if (call_prom("getprop", 4, 1, prom_chosen, "mmu",
> &prom_mmu, sizeof(prom_mmu)) <= 0) {
> prom_print(" no MMU found\n");
> } else if (call_prom_ret("call-method", 4, 4, result, "translate",
> prom_mmu, &_stext, 1) != 0) {
> prom_print(" (translate failed)\n");
> } else {
> /* We assume the phys. address size is 3 cells */
> phys = result[2];
> }
Can anybody comment, if this "broken translate method in the OF" would
still be needed for arch/powerpc?
Gerhard
--
Schon gehört? GMX hat einen genialen Phishing-Filter in die
Toolbar eingebaut! http://www.gmx.net/de/go/toolbar
^ permalink raw reply
* Re: [PATCH] powerpc/fsl_msi: Handle msi-available-ranges better
From: Kumar Gala @ 2011-03-15 17:58 UTC (permalink / raw)
To: Scott Wood; +Cc: devicetree-discuss, linuxppc-dev
In-Reply-To: <20110117202528.GB561@udp111988uds.am.freescale.net>
On Jan 17, 2011, at 2:25 PM, Scott Wood wrote:
> Now handles multiple ranges, doesn't make assumptions about interrupt
> specifier format, and doesn't claim interrupts that don't correspond =
to an
> available range.
>=20
> Also has some better error checking.
>=20
> The device tree binding is updated to clarify some existing =
assumptions.
>=20
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
> Documentation/powerpc/dts-bindings/fsl/msi-pic.txt | 9 ++-
> arch/powerpc/sysdev/fsl_msi.c | 92 =
++++++++++++--------
> 2 files changed, 64 insertions(+), 37 deletions(-)
applied
- k=
^ permalink raw reply
* Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
From: Sven Luther @ 2011-03-15 17:49 UTC (permalink / raw)
To: Gerhard Pircher; +Cc: nello martuscielli, linuxppc-dev, acrux_it
In-Reply-To: <20110315171448.100300@gmx.net>
On Tue, Mar 15, 2011 at 06:14:48PM +0100, Gerhard Pircher wrote:
>
> -------- Original-Nachricht --------
> > Datum: Tue, 15 Mar 2011 17:44:49 +0100
> > Von: nello martuscielli <ppc.addon@gmail.com>
> > An:
> > CC: linuxppc-dev@lists.ozlabs.org, "acrux @ cruxppc" <acrux_it@libero.it>
> > Betreff: Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
>
> > ok, it seems that no one is interested to fix Pegasos1 G3 600MHz
> > support.
> >
> > But if someone is capable (i don't have this skill) here what it
> > happens reading from serial debug console untill it freezes with
> > linux-2.6.36.4
> >
> > Pegasos Boot Strap (c) 2002 bplan GmbH
> > Running on CPU PVR:00083311
> > PLL setting : 00000001
> > Enable L1 ICache...
> > Done.
> > Setting ROM Defaults...
> > Done.
> > Configuring SDRAM...
> > 08000000
> > 10000000
> > Delaying...Done.
> > RAMSIZE = 18000000
> > 00000004
> > Reading W83194 : 00FFFFFFFFFF0000
> > Done.
> > Setting Front Side Bus to 100MHz...
> > Done.
> > Releasing IDE reset ...
> > Done.
> > Configuring Legacy Devices
> > Initializing KBD...
> > Done.
> > PLL setting : 00000003
> > 10000000
> > Done.
> > FFFFFFFF
> > BIOS: Stage 2 entered arg(FFFC0000,00000000,18000000)
> > BIOS: MachineInfo at 0FFFFE68
> > BIOS: set MemPool limit to BAT size (old=18000000 new=10000000)
> > BIOS: 0F6FFFE8 bytes added to mempool
> > LoadFromRFS: starting
> > LoadFromRFS: lib module 00 has abs load adr at 00C00000
> > CopyModule: start
> > CopyModule: load address : 00C00000
> > CopyModule: copy module to ram...done
> > ModuleCopy: expanding... done
> > LoadFromRFS: 00000001 modules out of 00000001 loaded
> > InitLib: start
> > InitLib: call module as OF
> > allocated g_e=0xFD00008 (len=19232)
> > install_root: pkg=0xFD53B90
> > after init_environ e=0xFD00008
> > running nvramrc...
> > after running nvramrc
> > no/bad nvramrc - performing default startup script
> > Bus addresses:
> > 253@2
> > I/O addresses:
> > 7936@FE002100
> > Memory addresses:
> > 127M@88040000
> > 1.3G@98000000
> > Prefetchable memory addresses:
> > install_ata_disk_driver: reg=0x1000
> > init_drive: reset controller 0x1000/0x100E
> > init_drive: allow 4-bits for heads
> > init_drive: select drive 0
> > init_drive: seccnt=0x1 sector=0x1 cyl_lo=0x0 cyl_hi=0x0
> > init_drive: error=0x1 status=0x50 status2=0x50
> > init_drive: identify drive: atapi=0
> > install_ata_disk_driver: return no error (0)
> > install_ata_disk_driver: reg=0x1000
> > init_drive: allow 4-bits for heads
> > init_drive: select drive 1
> > init_drive: seccnt=0x1 sector=0x1 cyl_lo=0x14 cyl_hi=0xEB
> > init_drive: error=0x1 status=0x0 status2=0x0
> > init_drive: identify drive: atapi=1
> > atapi_cmd: cmdlen=12
> > atapi_cmd: inlen=8 len=65534
> > install_ata_disk_driver: return no error (0)
> > install_ata_disk_driver: reg=0x1010
> > init_drive: reset controller 0x1010/0x101E
> > init_drive: allow 4-bits for heads
> > init_drive: select drive 0
> > init_drive: seccnt=0x20 sector=0x20 cyl_lo=0x20 cyl_hi=0x20
> > init_drive: error=0x20 status=0x20 status2=0x20
> > ATA-wait-ready: timeout: status=0x20
> > init_drive: failed
> > install_ata_disk_driver: reg=0x1010
> > init_drive: allow 4-bits for heads
> > init_drive: select drive 1
> > init_drive: seccnt=0x30 sector=0x30 cyl_lo=0x30 cyl_hi=0x30
> > init_drive: error=0x30 status=0x30 status2=0x30
> > ATA-wait-ready: timeout: status=0x30
> > init_drive: failed
> > Bus addresses:
> > 254@2
> > I/O addresses:
> > 8@FE001038
> > 3072@FE001400
> > 48K@FE004000
> > Memory addresses:
> > 1792@A0000100
> > 1.2G@A0001000
> > Prefetchable memory addresses:
> > 12M@FD400000
> > F_INSTALL_CONSOLE: BEGIN
> > F_INSTALL_CONSOLE: ALIASING SCREEN
> > F_INSTALL_CONSOLE: ALIASING KBD
> > EMULATION INT HANDLER ENTERED WITH:
> > INT NO: 15
> >
> > EAX=0003 EBX=1111 ECX=2222 EDX=3333 ESP=0000 EBP=5555 ESI=6666 EDI=7777
> > AX=4E08 BX=C505 CX=0003 DX=202A SP=6CAA BP=5555 SI=5CF9 DI=7777
> > DS=C000 ES=BAD0 SS=C000 CS=F000 IP=FE15 NV UP -- PL ZR NA PE NC
> > CS:IP = F4 C558 C000 0244 3000 0000 01B4 AC63 0200
> > UNHANDLED INT 10 FUNCTION 0007 WITHIN EMULATION
> > F_INSTALL_CONSOLE: END
> > auto-booting...
> > do_load: dev="" dlen=0 args="" alen=0
> > do_load: alstr=""
> > do_load: path doesn't start with /
> > do_load: <diag-device> == <eth>
> > do_load: no args..use the default
> > do_load: <diag-file> == <diag>
> > try_load: dev="eth" dlen=3 args="diag" alen=4
> > entering main read/eval loop...
> >
> > [...]
> > atapi_cmd: cmdlen=12
> > atapi_cmd: inlen=2048 len=2048
> > iso_walk: read: name="zImage.chrp" extent=0x44FD size=0x337272 ret=no
> > error
> > iso9660: return R_END
> > file_system: return end (-4089)
> > disk-label return len=3371634 ret=end (-4089)
> > ata_disk_close
> > disk-label close:
> > checking exec type Fcode
> > fcode_is_exec: load=0x400000 loadlen=3371634
> > checking exec type Forth
> > checking exec type ELF
> > f_go:
> > checking exec type Fcode
> > fcode_is_exec: load=0x400000 loadlen=3371634
> > checking exec type Forth
> > checking exec type ELF
> > alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914
> > alloc_constrained: min 0x0, max 0xFFFFFFFF, align 0x1000, mask
> > 0xFFFFFFFF, size 0x332000, addr 0x300000
> > alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1
> > 0xFD54910 u2 0xFD54914 u3 0xFD54918
> > alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x300000
> > size 0xFD00000
> > alloc_constrained: fsblock 0x0
> > alloc_constrained: addr[] 0x300000
> > alloc_constrained: bsize[] 0xFD00000
> > alloc_constrained: passed min check
> > alloc_constrained: addr 0x300000, align 0xFFF, off 0x69696969
> > sum 0x0
> > alloc_constrained: passed align check
> > alloc_constrained: passed max check
> > alloc_constrained: passed mask check
> > alloc_constrained: passed full size check
> > alloc_constrained: passed size check
> > alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914
> > alloc_constrained: min 0x0, max 0xFFFFFFFF, align 0x1000, mask
> > 0xFFFFFFFF, size 0x6883C0, addr 0x632000
> > alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1
> > 0xFD54910 u2 0xFD54914 u3 0xFD54918
> > alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x632000
> > size 0xF9CE000
> > alloc_constrained: fsblock 0x0
> > alloc_constrained: addr[] 0x632000
> > alloc_constrained: bsize[] 0xF9CE000
> > alloc_constrained: passed min check
> > alloc_constrained: addr 0x632000, align 0xFFF, off 0x0
> > sum 0x0
> > alloc_constrained: passed align check
> > alloc_constrained: passed max check
> > alloc_constrained: passed mask check
> > alloc_constrained: passed full size check
> > alloc_constrained: passed size check
> >
> >
> >
> > and here giving a try with a smaller (1.9MB) linux boot kernel
> > [...]
> > atapi_cmd: cmdlen=12
> > atapi_cmd: inlen=2048 len=2048
> > iso_walk: read: name="zImage.chrp" extent=0x3CC size=0x1D8A1A ret=no error
> > iso9660: return R_END
> > file_system: return end (-4089)
> > disk-label return len=1935898 ret=end (-4089)
> > ata_disk_close
> > disk-label close:
> > checking exec type Fcode
> > fcode_is_exec: load=0x400000 loadlen=1935898
> > checking exec type Forth
> > checking exec type ELF
> > f_go:
> > checking exec type Fcode
> > fcode_is_exec: load=0x400000 loadlen=1935898
> > checking exec type Forth
> > checking exec type ELF
> > alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914
> > alloc_constrained: min 0x0, max 0xFFFFFFFF, align 0x1000, mask
> > 0xFFFFFFFF, size 0x1D3000, addr 0x300000
> > alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1
> > 0xFD54910 u2 0xFD54914 u3 0xFD54918
> > alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x300000
> > size 0xFD00000
> > alloc_constrained: fsblock 0x0
> > alloc_constrained: addr[] 0x300000
> > alloc_constrained: bsize[] 0xFD00000
> > alloc_constrained: passed min check
> > alloc_constrained: addr 0x300000, align 0xFFF, off 0x69696969
> > sum 0x0
> > alloc_constrained: passed align check
> > alloc_constrained: passed max check
> > alloc_constrained: passed mask check
> > alloc_constrained: passed full size check
> > alloc_constrained: passed size check
> > alloc_aligned: a 0xFD548E8 align 0xFD5491C size 0xFD54918 addr 0xFD54914
> > alloc_constrained: min 0x0, max 0xFFFFFFFF, align 0x1000, mask
> > 0xFFFFFFFF, size 0x3AC9A0, addr 0x4D3000
> > alloc_constrained: acells 0x1 scells 0x1 t1 0xC t2 0xFD5490C u1
> > 0xFD54910 u2 0xFD54914 u3 0xFD54918
> > alloc_constrained: allocator_block 0xFD54930, next 0x0 addr 0x4D3000
> > size 0xFB2D000
> > alloc_constrained: fsblock 0x0
> > alloc_constrained: addr[] 0x4D3000
> > alloc_constrained: bsize[] 0xFB2D000
> > alloc_constrained: passed min check
> > alloc_constrained: addr 0x4D3000, align 0xFFF, off 0x0
> > sum 0x0
> > alloc_constrained: passed align check
> > alloc_constrained: passed max check
> > alloc_constrained: passed mask check
> > alloc_constrained: passed full size check
> > alloc_constrained: passed size check
>
> I don't know much about the Pegasos OF, but did you give GRUB2 for OF
> a try? Maybe it can boot a newer Linux kernel, if it is not a device
> tree related problem.
>
> On the other side you mentioned this workaround in
> arch/ppc/kernel/prom_init.c to me some time ago:
>
> unsigned long __init prom_init(int r3, int r4, prom_entry pp) :
> > node = call_prom("finddevice", 1, 1, "/");
> > rc = call_prom("getprop", 4, 1, node, "model", model, sizeof(model));
> > if (rc > 0 && !strncmp (model, "Pegasos", 7)
> > && strncmp (model, "Pegasos2", 8)) {
> > /* Pegasos 1 has a broken translate method in the OF,
> > * and furthermore the BATs are mapped 1:1 so the phys
> > * address calculated above is correct, so let's use
> > * it directly.
> > */
> > } else if (offset == 0) {
> > /* If we are already running at 0xc0000000, we assume we were
> > * loaded by an OF bootloader which did set a BAT for us.
> > * This breaks OF translate so we force phys to be 0.
> > */
> > prom_print("(already at 0xc0000000) phys=0\n");
> > phys = 0;
> > } else if (call_prom("getprop", 4, 1, prom_chosen, "mmu",
> > &prom_mmu, sizeof(prom_mmu)) <= 0) {
> > prom_print(" no MMU found\n");
> > } else if (call_prom_ret("call-method", 4, 4, result, "translate",
> > prom_mmu, &_stext, 1) != 0) {
> > prom_print(" (translate failed)\n");
> > } else {
> > /* We assume the phys. address size is 3 cells */
> > phys = result[2];
> > }
>
> Can anybody comment, if this "broken translate method in the OF" would
> still be needed for arch/powerpc?
Well, since this is long dead hardware not produced anymore, i don't see how the
OF could have unbroken itself by moving to powerpc.
It has been age since i looked into this, but to the best of my knowledge (and i
wrote the above code or at least the earlier versions) it should be still broken.
But YMMV, ...
Friendly,
Sven Luther
^ permalink raw reply
* Re: [PATCH] [v2] watchdog: booke_wdt: clean up status messages
From: Wim Van Sebroeck @ 2011-03-15 18:19 UTC (permalink / raw)
To: Kumar Gala; +Cc: wim, linux-watchdog, Timur Tabi, linuxppc-dev
In-Reply-To: <C8B1E427-5A9D-4ED2-9C39-C1D8201E636E@kernel.crashing.org>
Hi Kumar,
I allready had it in the watchdog tree for a couple of weeks (and thus also in linux-next).
Are you going to sent it of to Linus or will I sent it over via the watchdog tree?
Thanks in advance,
Wim.
>
> On Feb 8, 2011, at 5:39 PM, Timur Tabi wrote:
>
> > Improve the status messages that are displayed during some operations of the
> > PowerPC watchdog timer driver. When the watchdog is enabled, the timeout is
> > displayed as a number of seconds, instead of an obscure "period". The "period"
> > is the position of a bit in a 64-bit timer register. The higher the value,
> > the quicker the watchdog timeout occurs. Some people chose a high "period"
> > value for the timer and get confused as to why the board resets within a
> > few seconds.
> >
> > Messages displayed during open and close are now debug messages, so that they
> > don't clutter the console by default. Finally, printk() is replaced with the
> > pr_xxx() equivalent.
> >
> > Signed-off-by: Timur Tabi <timur@freescale.com>
> > ---
> > drivers/watchdog/booke_wdt.c | 19 +++++++++----------
> > 1 files changed, 9 insertions(+), 10 deletions(-)
>
> applied
>
> - k
^ permalink raw reply
* Re: [PATCH] [v2] watchdog: booke_wdt: clean up status messages
From: Kumar Gala @ 2011-03-15 18:47 UTC (permalink / raw)
To: Wim Van Sebroeck; +Cc: linux-watchdog, Timur Tabi, linuxppc-dev
In-Reply-To: <20110315181904.GM1751@infomag.iguana.be>
On Mar 15, 2011, at 1:19 PM, Wim Van Sebroeck wrote:
> Hi Kumar,
>=20
> I allready had it in the watchdog tree for a couple of weeks (and thus =
also in linux-next).
> Are you going to sent it of to Linus or will I sent it over via the =
watchdog tree?
>=20
> Thanks in advance,
> Wim.
I'll drop it from my tree.
- k=
^ permalink raw reply
* [PATCH] update name of pic-no-reset property
From: Stuart Yoder @ 2011-03-15 18:37 UTC (permalink / raw)
To: linuxppc-dev; +Cc: Stuart Yoder
From: Stuart Yoder <stuart.yoder@freescale.com>
-changed name from 'no-reset' to 'pic-not-reset' be consisent with
Meador Inge's open pic binding patch
-update definition
Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
---
Documentation/powerpc/dts-bindings/fsl/mpic.txt | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/Documentation/powerpc/dts-bindings/fsl/mpic.txt b/Documentation/powerpc/dts-bindings/fsl/mpic.txt
index fdf97c5..8b76e0f 100644
--- a/Documentation/powerpc/dts-bindings/fsl/mpic.txt
+++ b/Documentation/powerpc/dts-bindings/fsl/mpic.txt
@@ -44,7 +44,7 @@ PROPERTIES
Value type: <u32>
Definition: Shall be 0.
- - no-reset
+ - pic-no-reset
Usage: optional
Value type: <empty>
Definition: The presence of this property specifies that the
@@ -53,7 +53,10 @@ PROPERTIES
configuration registers to a sane state-- masked or
directed at other cores. This ensures that the client
program will not receive interrupts for sources not belonging
- to the client.
+ to the client. The presence of this property also mandates
+ that any initialization related to interrupt sources shall
+ be limited to sources explicitly referenced in the device tree.
+
INTERRUPT SPECIFIER DEFINITION
--
1.7.2.2
^ permalink raw reply related
* Re: [PATCH] update name of pic-no-reset property
From: Kumar Gala @ 2011-03-15 19:09 UTC (permalink / raw)
To: Stuart Yoder; +Cc: linuxppc-dev
In-Reply-To: <1300214278-1588-1-git-send-email-stuart.yoder@freescale.com>
On Mar 15, 2011, at 1:37 PM, Stuart Yoder wrote:
> From: Stuart Yoder <stuart.yoder@freescale.com>
>
> -changed name from 'no-reset' to 'pic-not-reset' be consisent with
> Meador Inge's open pic binding patch
> -update definition
>
> Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
> ---
> Documentation/powerpc/dts-bindings/fsl/mpic.txt | 7 +++++--
> 1 files changed, 5 insertions(+), 2 deletions(-)
applied, I squashed this with the mpic binding patch.
- k
^ permalink raw reply
* Re: [PATCH] powerpc: sysdev: fix signedness bug
From: Kumar Gala @ 2011-03-15 19:19 UTC (permalink / raw)
To: Vasiliy Kulikov
Cc: Harninder Rai, devicetree-discuss, kernel-janitors, linux-kernel,
Paul Mackerras, linuxppc-dev, Vivek Mahajan
In-Reply-To: <1287327102-9068-1-git-send-email-segooon@gmail.com>
On Oct 17, 2010, at 9:51 AM, Vasiliy Kulikov wrote:
> sram_params.sram_size and sram_params.sram_offset were unsigned.
> If get_cache_sram_size() or get_cache_sram_offset() returns error code
> then it is not seen to the caller. Made sram_size and sram_offset signed.
>
> Signed-off-by: Vasiliy Kulikov <segooon@gmail.com>
> ---
> arch/powerpc/sysdev/fsl_85xx_l2ctlr.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
applied
- k
^ permalink raw reply
* Re: [PATCH] powerpc/fsl-booke: Add e500mc smp defconfig
From: Kumar Gala @ 2011-03-15 19:23 UTC (permalink / raw)
To: Timur Tabi; +Cc: linuxppc-dev
In-Reply-To: <AANLkTinJq78ZQbW_r0mJqA884-Mt+a_m6pJSLn-PAGuT@mail.gmail.com>
On Oct 14, 2010, at 8:51 AM, Timur Tabi wrote:
> On Thu, Oct 14, 2010 at 8:25 AM, Kumar Gala =
<galak@kernel.crashing.org> wrote:
>=20
>> +CONFIG_MATH_EMULATION=3Dy
>=20
> Don't these chips have hardware FP?
removed.
>=20
>> +CONFIG_E1000=3Dy
>> +CONFIG_E1000E=3Dy
>=20
> Are you sure you want these on by default? We may use the E1000 cards
> in-house, but I don't know if our customers do.
leaving, customers can always disable
>> +CONFIG_MSDOS_FS=3Dm
>> +CONFIG_VFAT_FS=3Dy
>> +CONFIG_NTFS_FS=3Dy
leaving since we deal with USB flashes and MMC cards which could be =
MSDOS, VFAT, etc.
- k=
^ permalink raw reply
* Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
From: Gerhard Pircher @ 2011-03-15 20:08 UTC (permalink / raw)
To: Sven Luther; +Cc: ppc.addon, linuxppc-dev, acrux_it
In-Reply-To: <20110315174924.GA24001@z-innov.com>
-------- Original-Nachricht --------
> Datum: Tue, 15 Mar 2011 18:49:24 +0100
> Von: Sven Luther <sven@z-innov.com>
> An: Gerhard Pircher <gerhard_pircher@gmx.net>
> CC: nello martuscielli <ppc.addon@gmail.com>, linuxppc-dev@lists.ozlabs.org, acrux_it@libero.it
> Betreff: Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
> On Tue, Mar 15, 2011 at 06:14:48PM +0100, Gerhard Pircher wrote:
[...]
> > On the other side you mentioned this workaround in
> > arch/ppc/kernel/prom_init.c to me some time ago:
> >
> > unsigned long __init prom_init(int r3, int r4, prom_entry pp) :
> > > node = call_prom("finddevice", 1, 1, "/");
> > > rc = call_prom("getprop", 4, 1, node, "model", model,
> sizeof(model));
> > > if (rc > 0 && !strncmp (model, "Pegasos", 7)
> > > && strncmp (model, "Pegasos2", 8)) {
> > > /* Pegasos 1 has a broken translate method in the OF,
> > > * and furthermore the BATs are mapped 1:1 so the phys
> > > * address calculated above is correct, so let's use
> > > * it directly.
> > > */
> > > } else if (offset == 0) {
> > > /* If we are already running at 0xc0000000, we assume
> we were
> > > * loaded by an OF bootloader which did set a BAT for
> us.
> > > * This breaks OF translate so we force phys to be 0.
> > > */
> > > prom_print("(already at 0xc0000000) phys=0\n");
> > > phys = 0;
> > > } else if (call_prom("getprop", 4, 1, prom_chosen, "mmu",
> > > &prom_mmu, sizeof(prom_mmu)) <= 0) {
> > > prom_print(" no MMU found\n");
> > > } else if (call_prom_ret("call-method", 4, 4, result,
> "translate",
> > > prom_mmu, &_stext, 1) != 0) {
> > > prom_print(" (translate failed)\n");
> > > } else {
> > > /* We assume the phys. address size is 3 cells */
> > > phys = result[2];
> > > }
> >
> > Can anybody comment, if this "broken translate method in the OF" would
> > still be needed for arch/powerpc?
>
> Well, since this is long dead hardware not produced anymore, i don't see
> how the OF could have unbroken itself by moving to powerpc.
>
> It has been age since i looked into this, but to the best of my knowledge
> (and i wrote the above code or at least the earlier versions) it should
> be still broken.
Any idea then, how the workaround can be ported to arch/powerpc/ or if
there is a better one available?
regards,
Gerhard
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
^ permalink raw reply
* [git pull] Please pull powerpc.git next branch
From: Kumar Gala @ 2011-03-15 21:04 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: linuxppc-dev
The following changes since commit 964a29962c278ddff8a199f23d7c9ef35152a0fe:
powerpc/pseries: Disable MSI using new interface if possible (2011-03-11 14:18:24 +1100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/galak/powerpc.git next
Anatolij Gustschin (1):
powerpc/mpc8xxx_gpio: simplify searching for 'fsl, qoriq-gpio' compatiable
Holger Brunck (3):
powerpc/83xx: rename and update kmeter1
powerpc/82xx: rename and update mgcoge board support
powerpc/8xx: remove obsolete mgsuvd board
Julia Lawall (1):
drivers/serial/ucc_uart.c: Add of_node_put to avoid memory leak
Kumar Gala (1):
powerpc/85xx: Fix writing to spin table 'cpu-release-addr' on ppc64e
Liu Yu (1):
powerpc/85xx: Workaroudn e500 CPU erratum A005
Prabhakar Kushwaha (1):
powerpc/fsl_pci: Add support for FSL PCIe controllers v2.x
Scott Wood (1):
powerpc/fsl_msi: Handle msi-available-ranges better
Shan Hai (1):
powerpc/85xx: Fix SPE float to integer conversion failure
Stuart Yoder (1):
powerpc/fsl: define binding for fsl mpic interrupt controllers
Vasiliy Kulikov (1):
powerpc/85xx: Fix signedness bug in cache-sram
Vivek Mahajan (1):
powerpc/fsl: 85xx: document cache sram bindings
Xulei (2):
ATA: Add FSL sata v2 controller support
powerpc/85xx: Update sata controller compatible for p1022ds board
.../devicetree/bindings/powerpc/fsl/cache_sram.txt | 20 ++
.../devicetree/bindings/powerpc/fsl/mpic.txt | 253 ++++++++++++++++----
.../devicetree/bindings/powerpc/fsl/msi-pic.txt | 9 +-
arch/powerpc/boot/dts/kmeter1.dts | 69 +++---
arch/powerpc/boot/dts/mgcoge.dts | 47 ++--
arch/powerpc/boot/dts/mgsuvd.dts | 163 -------------
arch/powerpc/boot/dts/p1022ds.dts | 4 +-
arch/powerpc/configs/83xx/kmeter1_defconfig | 7 +-
arch/powerpc/configs/mgcoge_defconfig | 9 +-
arch/powerpc/configs/mgsuvd_defconfig | 81 -------
arch/powerpc/include/asm/reg.h | 2 +
arch/powerpc/math-emu/math_efp.c | 65 +++++-
arch/powerpc/platforms/82xx/Makefile | 2 +-
arch/powerpc/platforms/82xx/{mgcoge.c => km82xx.c} | 62 ++++--
arch/powerpc/platforms/83xx/Makefile | 2 +-
.../powerpc/platforms/83xx/{kmeter1.c => km83xx.c} | 46 +++--
arch/powerpc/platforms/85xx/smp.c | 6 +-
arch/powerpc/platforms/8xx/Kconfig | 6 -
arch/powerpc/platforms/8xx/Makefile | 1 -
arch/powerpc/platforms/8xx/mgsuvd.c | 92 -------
arch/powerpc/sysdev/fsl_85xx_l2ctlr.c | 4 +-
arch/powerpc/sysdev/fsl_msi.c | 92 +++++---
arch/powerpc/sysdev/fsl_pci.c | 15 +-
arch/powerpc/sysdev/fsl_pci.h | 17 +-
arch/powerpc/sysdev/mpc8xxx_gpio.c | 4 +-
drivers/ata/sata_fsl.c | 25 ++-
drivers/tty/serial/ucc_uart.c | 67 +++---
27 files changed, 584 insertions(+), 586 deletions(-)
create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/cache_sram.txt
delete mode 100644 arch/powerpc/boot/dts/mgsuvd.dts
delete mode 100644 arch/powerpc/configs/mgsuvd_defconfig
rename arch/powerpc/platforms/82xx/{mgcoge.c => km82xx.c} (69%)
rename arch/powerpc/platforms/83xx/{kmeter1.c => km83xx.c} (80%)
delete mode 100644 arch/powerpc/platforms/8xx/mgsuvd.c
^ permalink raw reply
* Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
From: Sven Luther @ 2011-03-15 21:41 UTC (permalink / raw)
To: Gerhard Pircher; +Cc: sven.luther, ppc.addon, linuxppc-dev, acrux_it
In-Reply-To: <20110315200855.240730@gmx.net>
On Tue, Mar 15, 2011 at 09:08:55PM +0100, Gerhard Pircher wrote:
>
> > Well, since this is long dead hardware not produced anymore, i don't see
> > how the OF could have unbroken itself by moving to powerpc.
> >
> > It has been age since i looked into this, but to the best of my knowledge
> > (and i wrote the above code or at least the earlier versions) it should
> > be still broken.
> Any idea then, how the workaround can be ported to arch/powerpc/ or if
> there is a better one available?
Sorry, it has been years since i looked these parts of the linux kernel, so i don't really
know how the arch/powerpc code handles this differently. Your best guess is to hunt for the
code yourself, and find the place. I don't remember though if debugging at that time is
easily possible though.
Friendly,
Sven Luther
^ permalink raw reply
* [PATCH] crypto: caam - de-CHIP-ify device tree compatibles
From: Kim Phillips @ 2011-03-15 21:52 UTC (permalink / raw)
To: linux-crypto, linuxppc-dev, devicetree-discuss
Cc: Scott Wood, Steve Cornelius, Kumar Gala, Herbert Xu
- all the integration parameters have been captured by the binding.
- the block name really uniquely identifies this hardware.
Some advocate putting SoC names everywhere in case software needs
to work around some chip-specific bug, but more precise SoC
information already exists in SVR, and board information already
exists in the top-level device tree node.
Note that sometimes the SoC name is a worse identifier than the
block version, as the block version can change between revisions
of the same SoC.
As a matter of historical reference, neither SEC versions 2.x
nor 3.x (driven by talitos) ever needed CHIP references.
Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
Cc: Kumar Gala <kumar.gala@freescale.com>
Cc: Scott Wood <scottwood@freescale.com>
---
.../devicetree/bindings/crypto/fsl-sec4.txt | 64 ++++++++------------
arch/powerpc/boot/dts/p4080ds.dts | 32 ++++-------
2 files changed, 37 insertions(+), 59 deletions(-)
diff --git a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
index 568aa3c..bf57ecd 100644
--- a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
+++ b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
@@ -38,7 +38,7 @@ in the memory partition devoted to a particular core. The P4080 has 4 JRs, so
up to 4 JRs can be configured; and all 4 JRs process requests in parallel.
=====================================================================
-P4080 SEC 4 Node
+SEC 4 Node
Description
@@ -53,7 +53,7 @@ PROPERTIES
- compatible
Usage: required
Value type: <string>
- Definition: Must include "fsl,p4080-sec-v4.0","fsl,sec-v4.0"
+ Definition: Must include "fsl,sec-v4.0"
- #address-cells
Usage: required
@@ -105,7 +105,7 @@ PROPERTIES
EXAMPLE
crypto@300000 {
- compatible = "fsl,p4080-sec-v4.0", "fsl,sec-v4.0";
+ compatible = "fsl,sec-v4.0";
#address-cells = <1>;
#size-cells = <1>;
reg = <0x300000 0x10000>;
@@ -115,7 +115,7 @@ EXAMPLE
};
=====================================================================
-P4080 Job Ring (JR) Node
+Job Ring (JR) Node
Child of the crypto node defines data processing interface to SEC 4
across the peripheral bus for purposes of processing
@@ -127,7 +127,7 @@ P4080 Job Ring (JR) Node
- compatible
Usage: required
Value type: <string>
- Definition: Must include "fsl,p4080-sec-v4.0-job-ring","fsl,sec-v4.0-job-ring"
+ Definition: Must include "fsl,sec-v4.0-job-ring"
- reg
Usage: required
@@ -163,8 +163,7 @@ P4080 Job Ring (JR) Node
EXAMPLE
jr@1000 {
- compatible = "fsl,p4080-sec-v4.0-job-ring",
- "fsl,sec-v4.0-job-ring";
+ compatible = "fsl,sec-v4.0-job-ring";
reg = <0x1000 0x1000>;
fsl,liodn = <0x081>;
interrupt-parent = <&mpic>;
@@ -173,7 +172,7 @@ EXAMPLE
=====================================================================
-P4080 Run Time Integrity Check (RTIC) Node
+Run Time Integrity Check (RTIC) Node
Child node of the crypto node. Defines a register space that
contains up to 5 sets of addresses and their lengths (sizes) that
@@ -186,7 +185,7 @@ P4080 Run Time Integrity Check (RTIC) Node
- compatible
Usage: required
Value type: <string>
- Definition: Must include "fsl,p4080-sec-v4.0-rtic","fsl,sec-v4.0-rtic".
+ Definition: Must include "fsl,sec-v4.0-rtic".
- #address-cells
Usage: required
@@ -219,8 +218,7 @@ P4080 Run Time Integrity Check (RTIC) Node
EXAMPLE
rtic@6000 {
- compatible = "fsl,p4080-sec-v4.0-rtic",
- "fsl,sec-v4.0-rtic";
+ compatible = "fsl,sec-v4.0-rtic";
#address-cells = <1>;
#size-cells = <1>;
reg = <0x6000 0x100>;
@@ -228,7 +226,7 @@ EXAMPLE
};
=====================================================================
-P4080 Run Time Integrity Check (RTIC) Memory Node
+Run Time Integrity Check (RTIC) Memory Node
A child node that defines individual RTIC memory regions that are used to
perform run-time integrity check of memory areas that should not modified.
The node defines a register that contains the memory address &
@@ -238,7 +236,7 @@ P4080 Run Time Integrity Check (RTIC) Memory Node
- compatible
Usage: required
Value type: <string>
- Definition: Must include "fsl,p4080-sec-v4.0-rtic-memory","fsl,sec-v4.0-rtic-memory".
+ Definition: Must include "fsl,sec-v4.0-rtic-memory".
- reg
Usage: required
@@ -270,15 +268,14 @@ P4080 Run Time Integrity Check (RTIC) Memory Node
EXAMPLE
rtic-a@0 {
- compatible = "fsl,p4080-sec-v4.0-rtic-memory",
- "fsl,sec-v4.0-rtic-memory";
+ compatible = "fsl,sec-v4.0-rtic-memory";
reg = <0x00 0x20 0x100 0x80>;
fsl,liodn = <0x03c>;
fsl,rtic-region = <0x12345678 0x12345678 0x12345678>;
};
=====================================================================
-P4080 Secure Non-Volatile Storage (SNVS) Node
+Secure Non-Volatile Storage (SNVS) Node
Node defines address range and the associated
interrupt for the SNVS function. This function
@@ -288,7 +285,7 @@ P4080 Secure Non-Volatile Storage (SNVS) Node
- compatible
Usage: required
Value type: <string>
- Definition: Must include "fsl,p4080-sec-v4.0-mon", "fsl,sec-v4.0-mon".
+ Definition: Must include "fsl,sec-v4.0-mon".
- reg
Usage: required
@@ -315,7 +312,7 @@ P4080 Secure Non-Volatile Storage (SNVS) Node
EXAMPLE
sec_mon@314000 {
- compatible = "fsl,p4080-sec-v4.0-mon", "fsl,sec-v4.0-mon";
+ compatible = "fsl,sec-v4.0-mon";
reg = <0x314000 0x1000>;
interrupt-parent = <&mpic>;
interrupts = <93 2>;
@@ -325,7 +322,7 @@ EXAMPLE
FULL EXAMPLE
crypto: crypto@300000 {
- compatible = "fsl,p4080-sec-v4.0", "fsl,sec-v4.0";
+ compatible = "fsl,sec-v4.0";
#address-cells = <1>;
#size-cells = <1>;
reg = <0x300000 0x10000>;
@@ -334,73 +331,64 @@ FULL EXAMPLE
interrupts = <92 2>;
sec_jr0: jr@1000 {
- compatible = "fsl,p4080-sec-v4.0-job-ring",
- "fsl,sec-v4.0-job-ring";
+ compatible = "fsl,sec-v4.0-job-ring";
reg = <0x1000 0x1000>;
interrupt-parent = <&mpic>;
interrupts = <88 2>;
};
sec_jr1: jr@2000 {
- compatible = "fsl,p4080-sec-v4.0-job-ring",
- "fsl,sec-v4.0-job-ring";
+ compatible = "fsl,sec-v4.0-job-ring";
reg = <0x2000 0x1000>;
interrupt-parent = <&mpic>;
interrupts = <89 2>;
};
sec_jr2: jr@3000 {
- compatible = "fsl,p4080-sec-v4.0-job-ring",
- "fsl,sec-v4.0-job-ring";
+ compatible = "fsl,sec-v4.0-job-ring";
reg = <0x3000 0x1000>;
interrupt-parent = <&mpic>;
interrupts = <90 2>;
};
sec_jr3: jr@4000 {
- compatible = "fsl,p4080-sec-v4.0-job-ring",
- "fsl,sec-v4.0-job-ring";
+ compatible = "fsl,sec-v4.0-job-ring";
reg = <0x4000 0x1000>;
interrupt-parent = <&mpic>;
interrupts = <91 2>;
};
rtic@6000 {
- compatible = "fsl,p4080-sec-v4.0-rtic",
- "fsl,sec-v4.0-rtic";
+ compatible = "fsl,sec-v4.0-rtic";
#address-cells = <1>;
#size-cells = <1>;
reg = <0x6000 0x100>;
ranges = <0x0 0x6100 0xe00>;
rtic_a: rtic-a@0 {
- compatible = "fsl,p4080-sec-v4.0-rtic-memory",
- "fsl,sec-v4.0-rtic-memory";
+ compatible = "fsl,sec-v4.0-rtic-memory";
reg = <0x00 0x20 0x100 0x80>;
};
rtic_b: rtic-b@20 {
- compatible = "fsl,p4080-sec-v4.0-rtic-memory",
- "fsl,sec-v4.0-rtic-memory";
+ compatible = "fsl,sec-v4.0-rtic-memory";
reg = <0x20 0x20 0x200 0x80>;
};
rtic_c: rtic-c@40 {
- compatible = "fsl,p4080-sec-v4.0-rtic-memory",
- "fsl,sec-v4.0-rtic-memory";
+ compatible = "fsl,sec-v4.0-rtic-memory";
reg = <0x40 0x20 0x300 0x80>;
};
rtic_d: rtic-d@60 {
- compatible = "fsl,p4080-sec-v4.0-rtic-memory",
- "fsl,sec-v4.0-rtic-memory";
+ compatible = "fsl,sec-v4.0-rtic-memory";
reg = <0x60 0x20 0x500 0x80>;
};
};
};
sec_mon: sec_mon@314000 {
- compatible = "fsl,p4080-sec-v4.0-mon", "fsl,sec-v4.0-mon";
+ compatible = "fsl,sec-v4.0-mon";
reg = <0x314000 0x1000>;
interrupt-parent = <&mpic>;
interrupts = <93 2>;
diff --git a/arch/powerpc/boot/dts/p4080ds.dts b/arch/powerpc/boot/dts/p4080ds.dts
index 0430d24..927f94d 100644
--- a/arch/powerpc/boot/dts/p4080ds.dts
+++ b/arch/powerpc/boot/dts/p4080ds.dts
@@ -423,7 +423,7 @@
};
crypto: crypto@300000 {
- compatible = "fsl,p4080-sec-v4.0", "fsl,sec-v4.0";
+ compatible = "fsl,sec-v4.0";
#address-cells = <1>;
#size-cells = <1>;
reg = <0x300000 0x10000>;
@@ -432,74 +432,64 @@
interrupts = <92 2>;
sec_jr0: jr@1000 {
- compatible = "fsl,p4080-sec-v4.0-job-ring",
- "fsl,sec-v4.0-job-ring";
+ compatible = "fsl,sec-v4.0-job-ring";
reg = <0x1000 0x1000>;
interrupt-parent = <&mpic>;
interrupts = <88 2>;
};
sec_jr1: jr@2000 {
- compatible = "fsl,p4080-sec-v4.0-job-ring",
- "fsl,sec-v4.0-job-ring";
+ compatible = "fsl,sec-v4.0-job-ring";
reg = <0x2000 0x1000>;
interrupt-parent = <&mpic>;
interrupts = <89 2>;
};
sec_jr2: jr@3000 {
- compatible = "fsl,p4080-sec-v4.0-job-ring",
- "fsl,sec-v4.0-job-ring";
+ compatible = "fsl,sec-v4.0-job-ring";
reg = <0x3000 0x1000>;
interrupt-parent = <&mpic>;
interrupts = <90 2>;
};
sec_jr3: jr@4000 {
- compatible = "fsl,p4080-sec-v4.0-job-ring",
- "fsl,sec-v4.0-job-ring";
+ compatible = "fsl,sec-v4.0-job-ring";
reg = <0x4000 0x1000>;
interrupt-parent = <&mpic>;
interrupts = <91 2>;
};
rtic@6000 {
- compatible = "fsl,p4080-sec-v4.0-rtic",
- "fsl,sec-v4.0-rtic";
+ compatible = "fsl,sec-v4.0-rtic";
#address-cells = <1>;
#size-cells = <1>;
reg = <0x6000 0x100>;
ranges = <0x0 0x6100 0xe00>;
rtic_a: rtic-a@0 {
- compatible = "fsl,p4080-sec-v4.0-rtic-memory",
- "fsl,sec-v4.0-rtic-memory";
+ compatible = "fsl,sec-v4.0-rtic-memory";
reg = <0x00 0x20 0x100 0x80>;
};
rtic_b: rtic-b@20 {
- compatible = "fsl,p4080-sec-v4.0-rtic-memory",
- "fsl,sec-v4.0-rtic-memory";
+ compatible = "fsl,sec-v4.0-rtic-memory";
reg = <0x20 0x20 0x200 0x80>;
};
rtic_c: rtic-c@40 {
- compatible = "fsl,p4080-sec-v4.0-rtic-memory",
- "fsl,sec-v4.0-rtic-memory";
+ compatible = "fsl,sec-v4.0-rtic-memory";
reg = <0x40 0x20 0x300 0x80>;
};
rtic_d: rtic-d@60 {
- compatible = "fsl,p4080-sec-v4.0-rtic-memory",
- "fsl,sec-v4.0-rtic-memory";
+ compatible = "fsl,sec-v4.0-rtic-memory";
reg = <0x60 0x20 0x500 0x80>;
};
};
};
sec_mon: sec_mon@314000 {
- compatible = "fsl,p4080-sec-v4.0-mon",
- "fsl,sec-v4.0-mon";
+ compatible = "fsl,sec-v4.0-mon";
reg = <0x314000 0x1000>;
interrupt-parent = <&mpic>;
interrupts = <93 2>;
--
1.7.4.1
^ permalink raw reply related
* Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
From: acrux @ 2011-03-16 0:23 UTC (permalink / raw)
To: Sven Luther; +Cc: ppc.addon, linuxppc-dev
In-Reply-To: <20110315214149.GA26249@z-innov.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 15 Mar 2011 22:41:49 +0100
Sven Luther <sven.luther@z-innov.com> wrote:
> On Tue, Mar 15, 2011 at 09:08:55PM +0100, Gerhard Pircher wrote:
> >
> > > Well, since this is long dead hardware not produced anymore, i
> > > don't see how the OF could have unbroken itself by moving to
> > > powerpc.
> > >
> > > It has been age since i looked into this, but to the best of my
> > > knowledge (and i wrote the above code or at least the earlier
> > > versions) it should be still broken.
> > Any idea then, how the workaround can be ported to arch/powerpc/ or
> > if there is a better one available?
>
> Sorry, it has been years since i looked these parts of the linux
> kernel, so i don't really know how the arch/powerpc code handles this
> differently. Your best guess is to hunt for the code yourself, and
> find the place. I don't remember though if debugging at that time is
> easily possible though.
>
if chrp support doesn't anymore include Pegasos1 it could be nice to
remove all that dead code. Albeit it's fun that nobody cared about for
it during the ppc=>powerpc switch as Pegasos1 was retired in 2003
and linux-2.6.17 was released in 2006... about three years.
my regards,
Nico
- --
GNU/Linux on Power Architecture
CRUX PPC - http://cruxppc.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
iEYEARECAAYFAk2AAvwACgkQxq34tDeO7LiAMgCfSOueU5IE+CGJQFm56C2vIQdl
WpUAn1MsjAZb/nt1SFtfiB1gLdx79lwX
=LULL
-----END PGP SIGNATURE-----
^ permalink raw reply
* Re: [PATCH] crypto: caam - de-CHIP-ify device tree compatibles
From: Grant Likely @ 2011-03-16 0:59 UTC (permalink / raw)
To: Kim Phillips
Cc: Herbert Xu, Steve Cornelius, devicetree-discuss, linux-crypto,
Scott Wood, linuxppc-dev, Kumar Gala
In-Reply-To: <20110315165220.d4fb60bc.kim.phillips@freescale.com>
On Tue, Mar 15, 2011 at 04:52:20PM -0500, Kim Phillips wrote:
> - all the integration parameters have been captured by the binding.
> - the block name really uniquely identifies this hardware.
>
> Some advocate putting SoC names everywhere in case software needs
> to work around some chip-specific bug, but more precise SoC
> information already exists in SVR, and board information already
> exists in the top-level device tree node.
>
> Note that sometimes the SoC name is a worse identifier than the
> block version, as the block version can change between revisions
> of the same SoC.
>
> As a matter of historical reference, neither SEC versions 2.x
> nor 3.x (driven by talitos) ever needed CHIP references.
>
> Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
<sigh> Very well. As long as some level of versioning is used on the
compatible values, I guess I can live with it.
Acked-off-by: Grant Likely <grant.likely@secretlab.ca>
> Cc: Kumar Gala <kumar.gala@freescale.com>
> Cc: Scott Wood <scottwood@freescale.com>
> ---
> .../devicetree/bindings/crypto/fsl-sec4.txt | 64 ++++++++------------
> arch/powerpc/boot/dts/p4080ds.dts | 32 ++++-------
> 2 files changed, 37 insertions(+), 59 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
> index 568aa3c..bf57ecd 100644
> --- a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
> +++ b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt
> @@ -38,7 +38,7 @@ in the memory partition devoted to a particular core. The P4080 has 4 JRs, so
> up to 4 JRs can be configured; and all 4 JRs process requests in parallel.
>
> =====================================================================
> -P4080 SEC 4 Node
> +SEC 4 Node
>
> Description
>
> @@ -53,7 +53,7 @@ PROPERTIES
> - compatible
> Usage: required
> Value type: <string>
> - Definition: Must include "fsl,p4080-sec-v4.0","fsl,sec-v4.0"
> + Definition: Must include "fsl,sec-v4.0"
>
> - #address-cells
> Usage: required
> @@ -105,7 +105,7 @@ PROPERTIES
>
> EXAMPLE
> crypto@300000 {
> - compatible = "fsl,p4080-sec-v4.0", "fsl,sec-v4.0";
> + compatible = "fsl,sec-v4.0";
> #address-cells = <1>;
> #size-cells = <1>;
> reg = <0x300000 0x10000>;
> @@ -115,7 +115,7 @@ EXAMPLE
> };
>
> =====================================================================
> -P4080 Job Ring (JR) Node
> +Job Ring (JR) Node
>
> Child of the crypto node defines data processing interface to SEC 4
> across the peripheral bus for purposes of processing
> @@ -127,7 +127,7 @@ P4080 Job Ring (JR) Node
> - compatible
> Usage: required
> Value type: <string>
> - Definition: Must include "fsl,p4080-sec-v4.0-job-ring","fsl,sec-v4.0-job-ring"
> + Definition: Must include "fsl,sec-v4.0-job-ring"
>
> - reg
> Usage: required
> @@ -163,8 +163,7 @@ P4080 Job Ring (JR) Node
>
> EXAMPLE
> jr@1000 {
> - compatible = "fsl,p4080-sec-v4.0-job-ring",
> - "fsl,sec-v4.0-job-ring";
> + compatible = "fsl,sec-v4.0-job-ring";
> reg = <0x1000 0x1000>;
> fsl,liodn = <0x081>;
> interrupt-parent = <&mpic>;
> @@ -173,7 +172,7 @@ EXAMPLE
>
>
> =====================================================================
> -P4080 Run Time Integrity Check (RTIC) Node
> +Run Time Integrity Check (RTIC) Node
>
> Child node of the crypto node. Defines a register space that
> contains up to 5 sets of addresses and their lengths (sizes) that
> @@ -186,7 +185,7 @@ P4080 Run Time Integrity Check (RTIC) Node
> - compatible
> Usage: required
> Value type: <string>
> - Definition: Must include "fsl,p4080-sec-v4.0-rtic","fsl,sec-v4.0-rtic".
> + Definition: Must include "fsl,sec-v4.0-rtic".
>
> - #address-cells
> Usage: required
> @@ -219,8 +218,7 @@ P4080 Run Time Integrity Check (RTIC) Node
>
> EXAMPLE
> rtic@6000 {
> - compatible = "fsl,p4080-sec-v4.0-rtic",
> - "fsl,sec-v4.0-rtic";
> + compatible = "fsl,sec-v4.0-rtic";
> #address-cells = <1>;
> #size-cells = <1>;
> reg = <0x6000 0x100>;
> @@ -228,7 +226,7 @@ EXAMPLE
> };
>
> =====================================================================
> -P4080 Run Time Integrity Check (RTIC) Memory Node
> +Run Time Integrity Check (RTIC) Memory Node
> A child node that defines individual RTIC memory regions that are used to
> perform run-time integrity check of memory areas that should not modified.
> The node defines a register that contains the memory address &
> @@ -238,7 +236,7 @@ P4080 Run Time Integrity Check (RTIC) Memory Node
> - compatible
> Usage: required
> Value type: <string>
> - Definition: Must include "fsl,p4080-sec-v4.0-rtic-memory","fsl,sec-v4.0-rtic-memory".
> + Definition: Must include "fsl,sec-v4.0-rtic-memory".
>
> - reg
> Usage: required
> @@ -270,15 +268,14 @@ P4080 Run Time Integrity Check (RTIC) Memory Node
>
> EXAMPLE
> rtic-a@0 {
> - compatible = "fsl,p4080-sec-v4.0-rtic-memory",
> - "fsl,sec-v4.0-rtic-memory";
> + compatible = "fsl,sec-v4.0-rtic-memory";
> reg = <0x00 0x20 0x100 0x80>;
> fsl,liodn = <0x03c>;
> fsl,rtic-region = <0x12345678 0x12345678 0x12345678>;
> };
>
> =====================================================================
> -P4080 Secure Non-Volatile Storage (SNVS) Node
> +Secure Non-Volatile Storage (SNVS) Node
>
> Node defines address range and the associated
> interrupt for the SNVS function. This function
> @@ -288,7 +285,7 @@ P4080 Secure Non-Volatile Storage (SNVS) Node
> - compatible
> Usage: required
> Value type: <string>
> - Definition: Must include "fsl,p4080-sec-v4.0-mon", "fsl,sec-v4.0-mon".
> + Definition: Must include "fsl,sec-v4.0-mon".
>
> - reg
> Usage: required
> @@ -315,7 +312,7 @@ P4080 Secure Non-Volatile Storage (SNVS) Node
>
> EXAMPLE
> sec_mon@314000 {
> - compatible = "fsl,p4080-sec-v4.0-mon", "fsl,sec-v4.0-mon";
> + compatible = "fsl,sec-v4.0-mon";
> reg = <0x314000 0x1000>;
> interrupt-parent = <&mpic>;
> interrupts = <93 2>;
> @@ -325,7 +322,7 @@ EXAMPLE
> FULL EXAMPLE
>
> crypto: crypto@300000 {
> - compatible = "fsl,p4080-sec-v4.0", "fsl,sec-v4.0";
> + compatible = "fsl,sec-v4.0";
> #address-cells = <1>;
> #size-cells = <1>;
> reg = <0x300000 0x10000>;
> @@ -334,73 +331,64 @@ FULL EXAMPLE
> interrupts = <92 2>;
>
> sec_jr0: jr@1000 {
> - compatible = "fsl,p4080-sec-v4.0-job-ring",
> - "fsl,sec-v4.0-job-ring";
> + compatible = "fsl,sec-v4.0-job-ring";
> reg = <0x1000 0x1000>;
> interrupt-parent = <&mpic>;
> interrupts = <88 2>;
> };
>
> sec_jr1: jr@2000 {
> - compatible = "fsl,p4080-sec-v4.0-job-ring",
> - "fsl,sec-v4.0-job-ring";
> + compatible = "fsl,sec-v4.0-job-ring";
> reg = <0x2000 0x1000>;
> interrupt-parent = <&mpic>;
> interrupts = <89 2>;
> };
>
> sec_jr2: jr@3000 {
> - compatible = "fsl,p4080-sec-v4.0-job-ring",
> - "fsl,sec-v4.0-job-ring";
> + compatible = "fsl,sec-v4.0-job-ring";
> reg = <0x3000 0x1000>;
> interrupt-parent = <&mpic>;
> interrupts = <90 2>;
> };
>
> sec_jr3: jr@4000 {
> - compatible = "fsl,p4080-sec-v4.0-job-ring",
> - "fsl,sec-v4.0-job-ring";
> + compatible = "fsl,sec-v4.0-job-ring";
> reg = <0x4000 0x1000>;
> interrupt-parent = <&mpic>;
> interrupts = <91 2>;
> };
>
> rtic@6000 {
> - compatible = "fsl,p4080-sec-v4.0-rtic",
> - "fsl,sec-v4.0-rtic";
> + compatible = "fsl,sec-v4.0-rtic";
> #address-cells = <1>;
> #size-cells = <1>;
> reg = <0x6000 0x100>;
> ranges = <0x0 0x6100 0xe00>;
>
> rtic_a: rtic-a@0 {
> - compatible = "fsl,p4080-sec-v4.0-rtic-memory",
> - "fsl,sec-v4.0-rtic-memory";
> + compatible = "fsl,sec-v4.0-rtic-memory";
> reg = <0x00 0x20 0x100 0x80>;
> };
>
> rtic_b: rtic-b@20 {
> - compatible = "fsl,p4080-sec-v4.0-rtic-memory",
> - "fsl,sec-v4.0-rtic-memory";
> + compatible = "fsl,sec-v4.0-rtic-memory";
> reg = <0x20 0x20 0x200 0x80>;
> };
>
> rtic_c: rtic-c@40 {
> - compatible = "fsl,p4080-sec-v4.0-rtic-memory",
> - "fsl,sec-v4.0-rtic-memory";
> + compatible = "fsl,sec-v4.0-rtic-memory";
> reg = <0x40 0x20 0x300 0x80>;
> };
>
> rtic_d: rtic-d@60 {
> - compatible = "fsl,p4080-sec-v4.0-rtic-memory",
> - "fsl,sec-v4.0-rtic-memory";
> + compatible = "fsl,sec-v4.0-rtic-memory";
> reg = <0x60 0x20 0x500 0x80>;
> };
> };
> };
>
> sec_mon: sec_mon@314000 {
> - compatible = "fsl,p4080-sec-v4.0-mon", "fsl,sec-v4.0-mon";
> + compatible = "fsl,sec-v4.0-mon";
> reg = <0x314000 0x1000>;
> interrupt-parent = <&mpic>;
> interrupts = <93 2>;
> diff --git a/arch/powerpc/boot/dts/p4080ds.dts b/arch/powerpc/boot/dts/p4080ds.dts
> index 0430d24..927f94d 100644
> --- a/arch/powerpc/boot/dts/p4080ds.dts
> +++ b/arch/powerpc/boot/dts/p4080ds.dts
> @@ -423,7 +423,7 @@
> };
>
> crypto: crypto@300000 {
> - compatible = "fsl,p4080-sec-v4.0", "fsl,sec-v4.0";
> + compatible = "fsl,sec-v4.0";
> #address-cells = <1>;
> #size-cells = <1>;
> reg = <0x300000 0x10000>;
> @@ -432,74 +432,64 @@
> interrupts = <92 2>;
>
> sec_jr0: jr@1000 {
> - compatible = "fsl,p4080-sec-v4.0-job-ring",
> - "fsl,sec-v4.0-job-ring";
> + compatible = "fsl,sec-v4.0-job-ring";
> reg = <0x1000 0x1000>;
> interrupt-parent = <&mpic>;
> interrupts = <88 2>;
> };
>
> sec_jr1: jr@2000 {
> - compatible = "fsl,p4080-sec-v4.0-job-ring",
> - "fsl,sec-v4.0-job-ring";
> + compatible = "fsl,sec-v4.0-job-ring";
> reg = <0x2000 0x1000>;
> interrupt-parent = <&mpic>;
> interrupts = <89 2>;
> };
>
> sec_jr2: jr@3000 {
> - compatible = "fsl,p4080-sec-v4.0-job-ring",
> - "fsl,sec-v4.0-job-ring";
> + compatible = "fsl,sec-v4.0-job-ring";
> reg = <0x3000 0x1000>;
> interrupt-parent = <&mpic>;
> interrupts = <90 2>;
> };
>
> sec_jr3: jr@4000 {
> - compatible = "fsl,p4080-sec-v4.0-job-ring",
> - "fsl,sec-v4.0-job-ring";
> + compatible = "fsl,sec-v4.0-job-ring";
> reg = <0x4000 0x1000>;
> interrupt-parent = <&mpic>;
> interrupts = <91 2>;
> };
>
> rtic@6000 {
> - compatible = "fsl,p4080-sec-v4.0-rtic",
> - "fsl,sec-v4.0-rtic";
> + compatible = "fsl,sec-v4.0-rtic";
> #address-cells = <1>;
> #size-cells = <1>;
> reg = <0x6000 0x100>;
> ranges = <0x0 0x6100 0xe00>;
>
> rtic_a: rtic-a@0 {
> - compatible = "fsl,p4080-sec-v4.0-rtic-memory",
> - "fsl,sec-v4.0-rtic-memory";
> + compatible = "fsl,sec-v4.0-rtic-memory";
> reg = <0x00 0x20 0x100 0x80>;
> };
>
> rtic_b: rtic-b@20 {
> - compatible = "fsl,p4080-sec-v4.0-rtic-memory",
> - "fsl,sec-v4.0-rtic-memory";
> + compatible = "fsl,sec-v4.0-rtic-memory";
> reg = <0x20 0x20 0x200 0x80>;
> };
>
> rtic_c: rtic-c@40 {
> - compatible = "fsl,p4080-sec-v4.0-rtic-memory",
> - "fsl,sec-v4.0-rtic-memory";
> + compatible = "fsl,sec-v4.0-rtic-memory";
> reg = <0x40 0x20 0x300 0x80>;
> };
>
> rtic_d: rtic-d@60 {
> - compatible = "fsl,p4080-sec-v4.0-rtic-memory",
> - "fsl,sec-v4.0-rtic-memory";
> + compatible = "fsl,sec-v4.0-rtic-memory";
> reg = <0x60 0x20 0x500 0x80>;
> };
> };
> };
>
> sec_mon: sec_mon@314000 {
> - compatible = "fsl,p4080-sec-v4.0-mon",
> - "fsl,sec-v4.0-mon";
> + compatible = "fsl,sec-v4.0-mon";
> reg = <0x314000 0x1000>;
> interrupt-parent = <&mpic>;
> interrupts = <93 2>;
> --
> 1.7.4.1
>
>
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
^ permalink raw reply
* linux-next: build failure after merge of the final tree (ubi tree related)
From: Stephen Rothwell @ 2011-03-16 6:50 UTC (permalink / raw)
To: Artem Bityutskiy; +Cc: linux-next, Paul Mackerras, linux-kernel, linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_write':
drivers/mtd/ubi/io.c:1348: error: 'PAGE_KERNEL' undeclared (first use in this function)
drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_all_ff':
drivers/mtd/ubi/io.c:1412: error: 'PAGE_KERNEL' undeclared (first use in this function)
Caused by commit 823ed5091113 ("UBI: allocate write checking buffer on demand").
I don't know how to fix this, so I have left it for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply
* Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
From: Sven Luther @ 2011-03-16 8:14 UTC (permalink / raw)
To: acrux; +Cc: Sven Luther, ppc.addon, linuxppc-dev
In-Reply-To: <20110316012319.b436ee11.acrux_it@libero.it>
On Wed, Mar 16, 2011 at 01:23:19AM +0100, acrux wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tue, 15 Mar 2011 22:41:49 +0100
> Sven Luther <sven.luther@z-innov.com> wrote:
>
> > On Tue, Mar 15, 2011 at 09:08:55PM +0100, Gerhard Pircher wrote:
> > >
> > > > Well, since this is long dead hardware not produced anymore, i
> > > > don't see how the OF could have unbroken itself by moving to
> > > > powerpc.
> > > >
> > > > It has been age since i looked into this, but to the best of my
> > > > knowledge (and i wrote the above code or at least the earlier
> > > > versions) it should be still broken.
> > > Any idea then, how the workaround can be ported to arch/powerpc/ or
> > > if there is a better one available?
> >
> > Sorry, it has been years since i looked these parts of the linux
> > kernel, so i don't really know how the arch/powerpc code handles this
> > differently. Your best guess is to hunt for the code yourself, and
> > find the place. I don't remember though if debugging at that time is
> > easily possible though.
> >
>
> if chrp support doesn't anymore include Pegasos1 it could be nice to
> remove all that dead code. Albeit it's fun that nobody cared about for
> it during the ppc=>powerpc switch as Pegasos1 was retired in 2003
> and linux-2.6.17 was released in 2006... about three years.
Also, the Pegasos2 OF implementation corrected these issues.
Notice that 2006 was also the year that debian sabotaged all powerpc work,
and had me expulsed because some people in the debian-installer team didn't
support technical critics and had more political pull inside debian than
myself. This happening after almost a decade of me giving my time to debian,
i kind of lost interest at that point, and nobody stepped up to take over my
work.
And on top of that, Franz Pop commited suicide last year, which could possibly
have been avoided if debian's leadership would have showed more maturity and
responsability back then.
Sorry for the off topic rant, but this is something which did take a really
long time for me to get over, and i believe that the debian folk are still not
ready to let it go. I am still censored on debian mailing lists today and probably
banned from irc channels.
Sadly,
Sven Luther
^ permalink raw reply
* Re: linux-next: build failure after merge of the final tree (ubi tree related)
From: Artem Bityutskiy @ 2011-03-16 7:22 UTC (permalink / raw)
To: ext Stephen Rothwell
Cc: linux-next, Paul Mackerras, linux-kernel, linuxppc-dev
In-Reply-To: <20110316175041.67c4f371.sfr@canb.auug.org.au>
On Wed, 2011-03-16 at 17:50 +1100, ext Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_write':
> drivers/mtd/ubi/io.c:1348: error: 'PAGE_KERNEL' undeclared (first use in this function)
> drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_all_ff':
> drivers/mtd/ubi/io.c:1412: error: 'PAGE_KERNEL' undeclared (first use in this function)
>
> Caused by commit 823ed5091113 ("UBI: allocate write checking buffer on demand").
>
> I don't know how to fix this, so I have left it for today.
Hmm, strange, include <linux/vmalloc.h> should be enough to use
__vmalloc with 'PAGE_KERNEL' AFAICS, and we have this include... I'll
try to look better.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
^ permalink raw reply
* Re: linux-next: build failure after merge of the final tree (ubi tree related)
From: Benjamin Herrenschmidt @ 2011-03-16 10:15 UTC (permalink / raw)
To: Artem.Bityutskiy
Cc: ext Stephen Rothwell, linux-next, Paul Mackerras, linux-kernel,
linuxppc-dev
In-Reply-To: <1300260170.2817.4.camel@localhost>
On Wed, 2011-03-16 at 09:22 +0200, Artem Bityutskiy wrote:
> On Wed, 2011-03-16 at 17:50 +1100, ext Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the final tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
> >
> > drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_write':
> > drivers/mtd/ubi/io.c:1348: error: 'PAGE_KERNEL' undeclared (first use in this function)
> > drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_all_ff':
> > drivers/mtd/ubi/io.c:1412: error: 'PAGE_KERNEL' undeclared (first use in this function)
> >
> > Caused by commit 823ed5091113 ("UBI: allocate write checking buffer on demand").
> >
> > I don't know how to fix this, so I have left it for today.
>
> Hmm, strange, include <linux/vmalloc.h> should be enough to use
> __vmalloc with 'PAGE_KERNEL' AFAICS, and we have this include... I'll
> try to look better.
Try adding asm/pgtable.h
Cheers,
Ben.
^ permalink raw reply
* Re: linux-next: build failure after merge of the final tree (ubi tree related)
From: Artem Bityutskiy @ 2011-03-16 10:27 UTC (permalink / raw)
To: Benjamin Herrenschmidt
Cc: ext Stephen Rothwell, linux-next, Paul Mackerras, linux-kernel,
linuxppc-dev
In-Reply-To: <1300270508.22236.1168.camel@pasglop>
On Wed, 2011-03-16 at 21:15 +1100, Benjamin Herrenschmidt wrote:
> On Wed, 2011-03-16 at 09:22 +0200, Artem Bityutskiy wrote:
> > On Wed, 2011-03-16 at 17:50 +1100, ext Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > After merging the final tree, today's linux-next build (powerpc
> > > allyesconfig) failed like this:
> > >
> > > drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_write':
> > > drivers/mtd/ubi/io.c:1348: error: 'PAGE_KERNEL' undeclared (first use in this function)
> > > drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_all_ff':
> > > drivers/mtd/ubi/io.c:1412: error: 'PAGE_KERNEL' undeclared (first use in this function)
> > >
> > > Caused by commit 823ed5091113 ("UBI: allocate write checking buffer on demand").
> > >
> > > I don't know how to fix this, so I have left it for today.
> >
> > Hmm, strange, include <linux/vmalloc.h> should be enough to use
> > __vmalloc with 'PAGE_KERNEL' AFAICS, and we have this include... I'll
> > try to look better.
>
> Try adding asm/pgtable.h
Thanks, that's what I was thinking about as well.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
^ permalink raw reply
* Re: linux-next: build failure after merge of the final tree (ubi tree related)
From: Artem Bityutskiy @ 2011-03-16 11:48 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, Paul Mackerras, linux-kernel, linuxppc-dev
In-Reply-To: <20110316175041.67c4f371.sfr@canb.auug.org.au>
On Wed, 2011-03-16 at 17:50 +1100, Stephen Rothwell wrote:
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_write':
> drivers/mtd/ubi/io.c:1348: error: 'PAGE_KERNEL' undeclared (first use in this function)
> drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_all_ff':
> drivers/mtd/ubi/io.c:1412: error: 'PAGE_KERNEL' undeclared (first use in this function)
>
> Caused by commit 823ed5091113 ("UBI: allocate write checking buffer on demand").
>
> I don't know how to fix this, so I have left it for today.
Fixed, sorry for the hassle and thank you!
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox