Board support for NextVoD - pdk7105

Board support for NextVoD - pdk7105

[John Paul Adrian Glaubitz]

[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]

Hi!

I'm currently playing around with a NextVoD box from Taiwan which is
a VoD system based on the ST40 SoC by ST Microelectronics:

root@nextvod01:~# cat /proc/cpuinfo
machine		: pdk7105
processor	: 0
cpu family	: sh4
cpu variant	: st40-300
cpu type	: STx7105
cut		: 3.x
cpu flags	: fpu icbi synco fpchg
cache type	: split (harvard)
icache size	: 32KiB (2-way)
dcache size	: 32KiB (2-way)
address sizes	: 32 bits physical
bogomips	: 448.51
root@nextvod01:~#

Attaching the output from dmesg and the current kernel config.gz.

The machine is currently running a rather old kernel which I would like
to update, however I'm not sure whether the necessary patches have been
upstreamed. There is a git repository available which has 2.6.32 kernel
with the necessary patches [1].

Do you think we could get this merged into the normal SH kernel?

Adrian

> [1] https://github.com/suzuke/kernel-pdk7105

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

[-- Attachment #2: nextvod-config.gz --]
[-- Type: application/gzip, Size: 15614 bytes --]

[-- Attachment #3: nextvod-dmesg.txt --]
[-- Type: text/plain, Size: 11093 bytes --]

Linux version 2.6.32.59_stm24_0211-PDK7105-32BITS (suzuke@suzuke-x220i) (gcc version 4.2.4 (snapshot) (STMicroelectronics/Linux Base 4.2.4-73)) #7 PREEMPT Fri Sep 27 23:53:25 CST 2013
Boot params:
... MOUNT_ROOT_RDONLY - 00000001
... RAMDISK_FLAGS     - 00000000
... ORIG_ROOT_DEV     - 00000200
... LOADER_TYPE       - 00000000
... INITRD_START      - 00000000
... INITRD_SIZE       - 00000000
Booting machvec: pdk7105
Node 0: start_pfn = 0x40000, low = 0x50000
Zone PFN ranges:
  Normal   0x00040000 -> 0x00050000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00040000 -> 0x00050000
On node 0 totalpages: 65536
free_area_init_node: node 0, pgdat 80e82ac0, node_mem_map 80ede000
  Normal zone: 512 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 65024 pages, LIFO batch:15
STMicroelectronics PDK7105-SDK board initialisation

STx7105 version 3.x
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyAS0,115200 rootdelay=0 root=/dev/sda2 rootfstype=ext4 rw rootflags=data=journal nwhwconf=device:eth0,hwaddr:24:cf:21:b2:6c:0d phyaddr:0,watchdog:5000 mem=256M bigphysarea=2048
bpa2: partition 'bigphysarea' created at 0x410e0000, size 8192 kB (0x00800000 B)
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
PVR=04909200 CVR=60880000 PRR=00009e20
I-cache : n_ways=2 n_sets=512 way_incr=16384
I-cache : entry_mask=0x00003fe0 alias_mask=0x00003000 n_aliases=4
D-cache : n_ways=2 n_sets=512 way_incr=16384
D-cache : entry_mask=0x00003fe0 alias_mask=0x00003000 n_aliases=4
Memory: 236288k/262144k available (4756k kernel code, 1911k data, 188k init)
Hierarchical RCU implementation.
NR_IRQS:600
Failed to enable clk CLKA_REF, ignoring
Failed to enable clk CLKA_PLL0LS, ignoring
Console: colour dummy device 80x25
console [ttyAS0] enabled
sh_tmu: TMU0 used for clock events
sh_tmu: TMU0 used for periodic clock events
sh_tmu: TMU1 used as clock source
Calibrating delay loop... 448.51 BogoMIPS (lpj=897024)
Mount-cache hash table entries: 512
CPU: STx7105
devtmpfs: initialized
[STM][PM-Sys]: ilc3 @ 4096
NET: Registered protocol family 16
Configuring FLASH for boot-from-spi: boot_mode=2
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
DMA: Registering DMA API.
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource TMU1
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
[STM]: [CPUFreq] Registered
[STM]: [PM]: Suspend support registered
cpufreq: SuperH CPU frequency driver.
Slow work thread pool: Starting up
Slow work thread pool: Ready
NTFS driver 2.1.29 [Flags: R/O].
JFFS2 version 2.2. (NAND) \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc.
ROMFS MTD (C) 2007 Red Hat, Inc.
fuse init (API version 7.13)
msgmni has been set to 461
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
lirc_dev: IR Remote Control driver registered, major 61 
lirc-stm: probe found data for platform device lirc-stm
lirc-stm: STM LIRC plugin using IRQ 125 in IR mode
lirc_dev: lirc_register_driver: sample_rate: 0
STMicroelectronics LIRC driver initialized.
STMicroelectronics ASC driver initialized
stm-asc.0: ttyAS0 at MMIO 0xfd032000 (irq = 121) is a stm-asc
brd: module loaded
loop: module loaded
nbd: registered device at major 43
Uniform Multi-Platform E-IDE driver
ide-gd driver 1.18
sata-stm version 0.8
sata-stm using hardware scatter/gather
sata-stm SATA version 1.90 DMA version 2.10
MiPHY driver style MiPHY3-65 probed successfully
MiPHY3-65, c1.5 Claimed by sata-stm 
scsi0 : sata-stm
ata1: SATA max UDMA/133 irq 72
ata1: SATA link down (SStatus 0 SControl 0)
stmmac - user ID: 0x10, Synopsys ID: 0x33
 No HW DMA feature register supported
 Enhanced/Alternate descriptors
 RX Checksum Offload Engine supported
 TX Checksum insertion supported
 Wake-Up On Lan supported
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
PPPoL2TP kernel driver, V1.0
nwhw_config: (eth0) setting mac address: 24:cf:21:b2:6c:0d
usbmon: debugfs is not available
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
stm_usb_probe: usb_phy_clk clock not found for stm-usb.0
stm-ehci stm-ehci.0: STMicroelectronics EHCI Host Controller
stm-ehci stm-ehci.0: new USB bus registered, assigned bus number 1
stm-ehci stm-ehci.0: irq 169, io mem 0xfe1ffe00
stm-ehci stm-ehci.0: USB 0.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
stm-ohci stm-ohci.0: STMicroelectronics OHCI Host Controller
stm-ohci stm-ohci.0: new USB bus registered, assigned bus number 2
stm-ohci stm-ohci.0: irq 168, io mem 0xfe1ffc00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
stm_usb_probe: usb_phy_clk clock not found for stm-usb.1
stm-ehci stm-ehci.1: STMicroelectronics EHCI Host Controller
stm-ehci stm-ehci.1: new USB bus registered, assigned bus number 3
stm-ehci stm-ehci.1: irq 143, io mem 0xfeaffe00
stm-ehci stm-ehci.1: USB 0.0 started, EHCI 1.00
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 1 port detected
stm-ohci stm-ohci.1: STMicroelectronics OHCI Host Controller
stm-ohci stm-ohci.1: new USB bus registered, assigned bus number 4
stm-ohci stm-ohci.1: irq 142, io mem 0xfeaffc00
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 1 port detected
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver microtekX6
mice: PS/2 mouse device common for all mice
I2O subsystem v1.325
i2o: max drivers = 8
i2c /dev entries driver
Linux video capture interface: v2.00
pwc: Philips webcam module version 10.0.13 loaded.
pwc: Supports Philips PCA645/646, PCVC675/680/690, PCVC720[40]/730/740/750 & PCVC830/840.
pwc: Also supports the Askey VC010, various Logitech Quickcams, Samsung MPC-C10 and MPC-C30,
pwc: the Creative WebCam 5 & Pro Ex, SOTEC Afina Eye and Visionite VCS-UC300 and VCS-UM100.
usbcore: registered new interface driver Philips webcam
gspca: main v2.7.0 registered
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
cpuidle: using governor ladder
sh_tmu: TMU0 kept as earlytimer
sh_tmu: TMU1 kept as earlytimer
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
[STM][PM-Sys]: emi @ 40
[STM][PM-Sys]: gpio @ 20
[STM][PM-Sys]: sysconf @ 10
[STM][PM-Sys]: clk @ 30
usb 1-1: new high speed USB device using stm-ehci and address 2
STMicroelectronics - Coprocessors st231 Init
st-coprocessor-0: No RAM reserved
st-coprocessor-1: No RAM reserved
DMA: Registering fdma_dmac.0 handler (16 channels).
IRQ 140/fdma_dmac.0: IRQF_DISABLED is not guaranteed on shared IRQs
stm-fdma stm-fdma.0: firmware: using built-in firmware fdma_STx7105_0.elf
DMA: Registering fdma_dmac.1 handler (16 channels).
platform fdma_dmac.0: SLIM hw 0.0, FDMA fw 2.3
IRQ 141/fdma_dmac.1: IRQF_DISABLED is not guaranteed on shared IRQs
stm-fdma stm-fdma.1: firmware: using built-in firmware fdma_STx7105_1.elf
platform fdma_dmac.1: SLIM hw 0.0, FDMA fw 2.6
stm-rng hardware driver 1.0 configured
Advanced Linux Sound Architecture Driver Version 1.0.21.
usbcore: registered new interface driver snd-usb-audio
usbcore: registered new interface driver snd-usb-caiaq
No device for DAI AD73311
Asahi Kasei AK4104 ALSA SoC Codec Driver
No device for DAI AK4535
Cirrus Logic CS4270 ALSA SoC Codec Driver
No device for DAI PCM3008 HiFi
No device for DAI SSM2602
No device for DAI tlv320aic23
usb 1-1: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
No device for DAI UDA134X
No device for DAI WM8510 HiFi
No device for DAI WM8728
No device for DAI WM8750
No device for DAI WM8971
No device for DAI WM8990 ADC/DAC Primary
ALSA device list:
  #0: STMicroelectronics STx7105 cut 3.x SOC audio subsystem
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (3694 buckets, 14776 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
scsi 1:0:0:0: Direct-Access     General  USB Flash Disk   1100 PQ: 0 ANSI: 0 CCS
sd 1:0:0:0: [sda] 15679488 512-byte logical blocks: (8.02 GB/7.47 GiB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete
sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00
sd 1:0:0:0: [sda] Assuming drive cache: write through
sd 1:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1 sda2
sd 1:0:0:0: [sda] Assuming drive cache: write through
sd 1:0:0:0: [sda] Attached SCSI removable disk
EXT4-fs (sda2): Ignoring delalloc option - requested data journaling mode
EXT4-fs (sda2): mounted filesystem with journalled data mode
VFS: Mounted root (ext4 filesystem) on device 8:2.
devtmpfs: mounted
Freeing unused kernel memory: 188k freed
<30>udevd[860]: starting version 175
eth0: device MAC address 24:cf:21:b2:6c:0d
STMMAC MII Bus: probed
eth0: PHY ID 01018f2d at 17 IRQ 0 (0:11) active
stmmac_timer: (eth0) sh_tmu Timer (freq 256Hz)
 No MAC Management Counters available
PHY: 0:11 - Link is Up - 100/Full
usb 3-1: new high speed USB device using stm-ehci and address 2
usb 3-1: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 2:0:0:0: Direct-Access     MUSHKIN  MKNUFDAM64GB     PMAP PQ: 0 ANSI: 6
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] 121012224 512-byte logical blocks: (61.9 GB/57.7 GiB)
usb-storage: device scan complete
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Attached SCSI removable disk

Re: Board support for NextVoD - pdk7105

[Rich Felker]

On Wed, Aug 03, 2016 at 11:59:27AM +0200, John Paul Adrian Glaubitz wrote:
> Hi!
> 
> I'm currently playing around with a NextVoD box from Taiwan which is
> a VoD system based on the ST40 SoC by ST Microelectronics:
> 
> root@nextvod01:~# cat /proc/cpuinfo
> machine		: pdk7105
> processor	: 0
> cpu family	: sh4
> cpu variant	: st40-300
> cpu type	: STx7105
> cut		: 3.x
> cpu flags	: fpu icbi synco fpchg
> cache type	: split (harvard)
> icache size	: 32KiB (2-way)
> dcache size	: 32KiB (2-way)
> address sizes	: 32 bits physical
> bogomips	: 448.51
> root@nextvod01:~#
> 
> Attaching the output from dmesg and the current kernel config.gz.
> 
> The machine is currently running a rather old kernel which I would like
> to update, however I'm not sure whether the necessary patches have been
> upstreamed. There is a git repository available which has 2.6.32 kernel
> with the necessary patches [1].
> 
> Do you think we could get this merged into the normal SH kernel?

I've got my replacement NextVoD setup more properly now and ready for
development work. Is this the source for the kernel you're using and
shipped with it? The repo does not seem to be based off upstream
kernel git at all, but rather a new repo starting with some
already-modified 2.6.32 tree as the initial commit.

If this is the right starting point, I'll pull the initial commit from
it and start diffing it against STlinux 2.4's "2.6.32" (which is
itself already modified and probably contains a lot of prereqs; src is
available as srpm at http://archive.stlinux.com/stlinux/2.4/SRPMS/),
and see if I can determine what the actual changes are.

This could be a good direction for future of arch/sh -- presumably all
the ST SoCs have a lot in common and could probably be a good first
target for supporting with device tree rather than legacy-style board
files full of platform devices.

Rich

Re: Board support for NextVoD - pdk7105

[John Paul Adrian Glaubitz]

Hi!

On 04/25/2018 08:30 PM, Rich Felker wrote:
> I've got my replacement NextVoD setup more properly now and ready for
> development work.

Cool \o/.

> Is this the source for the kernel you're using and
> shipped with it? The repo does not seem to be based off upstream
> kernel git at all, but rather a new repo starting with some
> already-modified 2.6.32 tree as the initial commit.

The kernel on the device is based on this source:

> https://github.com/dlintw/kernel-pdk7105

which is based on the ST-Linux kernel from:

> http://archive.stlinux.com/stlinux/2.4/SRPMS/index.html

There also is a 3.4 version:

> https://github.com/dlintw/pdk7105-3.4

But I haven't got it to build yet.

> If this is the right starting point, I'll pull the initial commit from
> it and start diffing it against STlinux 2.4's "2.6.32" (which is
> itself already modified and probably contains a lot of prereqs; src is
> available as srpm at http://archive.stlinux.com/stlinux/2.4/SRPMS/),
> and see if I can determine what the actual changes are.

Yeah. I think that sounds reasonable.

FWIW, the ST-40 stuff was already part of the Linux kernel but
it was removed at some point:

> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?idù6691872439ab2071171d4531c4a95b5d493ae5

> This could be a good direction for future of arch/sh -- presumably all
> the ST SoCs have a lot in common and could probably be a good first
> target for supporting with device tree rather than legacy-style board
> files full of platform devices.

Device tree would be really cool to have for more SH devices.

@Yoshinori: Is there any chance the LANDISK device tree patches can
             get merged at some point?

Adrian

-- 
  .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Board support for NextVoD - pdk7105

[Rich Felker]

On Thu, Apr 26, 2018 at 03:23:45PM +0200, John Paul Adrian Glaubitz wrote:
> Hi!
> 
> On 04/25/2018 08:30 PM, Rich Felker wrote:
> >I've got my replacement NextVoD setup more properly now and ready for
> >development work.
> 
> Cool \o/.
> 
> >Is this the source for the kernel you're using and
> >shipped with it? The repo does not seem to be based off upstream
> >kernel git at all, but rather a new repo starting with some
> >already-modified 2.6.32 tree as the initial commit.
> 
> The kernel on the device is based on this source:
> 
> >https://github.com/dlintw/kernel-pdk7105
> 
> which is based on the ST-Linux kernel from:
> 
> >http://archive.stlinux.com/stlinux/2.4/SRPMS/index.html
> 
> There also is a 3.4 version:
> 
> >https://github.com/dlintw/pdk7105-3.4
> 
> But I haven't got it to build yet.
> 
> >If this is the right starting point, I'll pull the initial commit from
> >it and start diffing it against STlinux 2.4's "2.6.32" (which is
> >itself already modified and probably contains a lot of prereqs; src is
> >available as srpm at http://archive.stlinux.com/stlinux/2.4/SRPMS/),
> >and see if I can determine what the actual changes are.
> 
> Yeah. I think that sounds reasonable.
> 
> FWIW, the ST-40 stuff was already part of the Linux kernel but
> it was removed at some point:
> 
> >https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?idù6691872439ab2071171d4531c4a95b5d493ae5

Thanks. This info is all very helpful. Especially the removal commit
gives a good idea what the minimal subset of the STlinux fork needed
to get something to work might be.

> >This could be a good direction for future of arch/sh -- presumably all
> >the ST SoCs have a lot in common and could probably be a good first
> >target for supporting with device tree rather than legacy-style board
> >files full of platform devices.
> 
> Device tree would be really cool to have for more SH devices.
> 
> @Yoshinori: Is there any chance the LANDISK device tree patches can
>             get merged at some point?

I'd like to move forward with them; the main thing that blocked me was
that some of the device tree changes were incompatible with how we're
using DT already on J2. One I recall was just changes in how the boot
commandline is handled, which can probably be omitted or made
non-breaking with minor changes.

The big issue I think we need to resolve consistently is what
"physical addresses" mean on models with MMU -- P1 (or whichever one
it is) segment-based addresses, or physical addresses in the sense of
what goes in the TLB entries. I think it should probably be the latter
but I'm not sure.

Rich

Re: Board support for NextVoD - pdk7105

[Rob Landley]

On 04/25/2018 01:30 PM, Rich Felker wrote:
> On Wed, Aug 03, 2016 at 11:59:27AM +0200, John Paul Adrian Glaubitz wrote:
>> Hi!
>>
>> I'm currently playing around with a NextVoD box from Taiwan which is
>> a VoD system based on the ST40 SoC by ST Microelectronics:
>>
>> root@nextvod01:~# cat /proc/cpuinfo
>> machine		: pdk7105
>> processor	: 0
>> cpu family	: sh4
>> cpu variant	: st40-300
>> cpu type	: STx7105
>> cut		: 3.x
>> cpu flags	: fpu icbi synco fpchg
>> cache type	: split (harvard)
>> icache size	: 32KiB (2-way)
>> dcache size	: 32KiB (2-way)
>> address sizes	: 32 bits physical
>> bogomips	: 448.51
>> root@nextvod01:~#
>>
>> Attaching the output from dmesg and the current kernel config.gz.
>>
>> The machine is currently running a rather old kernel which I would like
>> to update, however I'm not sure whether the necessary patches have been
>> upstreamed. There is a git repository available which has 2.6.32 kernel
>> with the necessary patches [1].
>>
>> Do you think we could get this merged into the normal SH kernel?
> 
> I've got my replacement NextVoD setup more properly now and ready for
> development work. Is this the source for the kernel you're using and
> shipped with it? The repo does not seem to be based off upstream
> kernel git at all, but rather a new repo starting with some
> already-modified 2.6.32 tree as the initial commit.

I have the box you sent me sitting on the shelf at home until I can get a power
supply and serial adapter for it.

Can we get a web page (wiki page) somewhere with info on this thing? I spent
half an hour trawling through the emails you guys cc'd me on back in january
about the first board Rich got, and... let's see:

> I have pre-installed Debian Wheezy onto your box. Once you power
> it up and hook it up to the network, it should boot into Debian
> Wheezy, the boot is finished once the LED has turned from purple
> to solid blue.
> 
> You will be able to login via SSH using root/root.
> 
> The box was installed using the image "wheezy-sh4.dd" linked here:
> 
>> https://github.com/fuyuanli/nextvod-linux-manual/blob/master/doc/02.01.md
> 
> Original firmware can be found here:
> 
>> https://code.google.com/p/nexttv-mod/downloads/detail?name=U-boot_sourcecode.zip
> 
> And the original stlinux distribution is to be found here:
> 
>> http://archive.stlinux.com/stlinux/index.html
> 

> 
> Some stuff can be found here:
> 
>> https://github.com/OpenSH4
>> https://github.com/dlintw/nextvod-tdt
>> https://github.com/dlintw/sh4twbox-build-env
>> https://github.com/dlintw/sh4twbox-multiboot
> 
> The kernel is here:
> 
>> https://github.com/dlintw/kernel-pdk7105
> 
> And I just found there is apparently a more modern kernel:
> 
>> https://github.com/dlintw/pdk7105-3.4

Ooh, did you send one to Sato-san too? (Or is he just cc'd?)

And there was more about the serial adapter but that boiled down to
"Rich offered to mail me a cable" so I don't have a window open for
that.

Info about where these boards _come_ from and so on would be nice.
"Ask Adrian to mail you one" seems unlikely to scale.

And I already asked if there was an existing community of
devs banging on these in China (seems like, since so much stuff is
translated) that we could maybe talk to...

(It's a fun little board. Bit like the original linksys, only
smaller and with video outputs. I look forward to powering it on.)

> This could be a good direction for future of arch/sh -- presumably all
> the ST SoCs have a lot in common and could probably be a good first
> target for supporting with device tree rather than legacy-style board
> files full of platform devices.

Rich, I'll see if I can get you one of the SH7760 boards I'm working
on at this contract, but it won't happen this month.

Rob

Re: Board support for NextVoD - pdk7105

[Rich Felker]

On Sun, Apr 29, 2018 at 11:58:28AM -0500, Rob Landley wrote:
> 
> 
> On 04/25/2018 01:30 PM, Rich Felker wrote:
> > On Wed, Aug 03, 2016 at 11:59:27AM +0200, John Paul Adrian Glaubitz wrote:
> >> Hi!
> >>
> >> I'm currently playing around with a NextVoD box from Taiwan which is
> >> a VoD system based on the ST40 SoC by ST Microelectronics:
> >>
> >> root@nextvod01:~# cat /proc/cpuinfo
> >> machine		: pdk7105
> >> processor	: 0
> >> cpu family	: sh4
> >> cpu variant	: st40-300
> >> cpu type	: STx7105
> >> cut		: 3.x
> >> cpu flags	: fpu icbi synco fpchg
> >> cache type	: split (harvard)
> >> icache size	: 32KiB (2-way)
> >> dcache size	: 32KiB (2-way)
> >> address sizes	: 32 bits physical
> >> bogomips	: 448.51
> >> root@nextvod01:~#
> >>
> >> Attaching the output from dmesg and the current kernel config.gz.
> >>
> >> The machine is currently running a rather old kernel which I would like
> >> to update, however I'm not sure whether the necessary patches have been
> >> upstreamed. There is a git repository available which has 2.6.32 kernel
> >> with the necessary patches [1].
> >>
> >> Do you think we could get this merged into the normal SH kernel?
> > 
> > I've got my replacement NextVoD setup more properly now and ready for
> > development work. Is this the source for the kernel you're using and
> > shipped with it? The repo does not seem to be based off upstream
> > kernel git at all, but rather a new repo starting with some
> > already-modified 2.6.32 tree as the initial commit.
> 
> I have the box you sent me sitting on the shelf at home until I can get a power
> supply and serial adapter for it.
> 
> Can we get a web page (wiki page) somewhere with info on this thing? I spent
> half an hour trawling through the emails you guys cc'd me on back in january
> about the first board Rich got, and... let's see:

The linux-sh.org wiki is mysteriously back! It seems like it would be
the obvious place to put this information. We should find out who is
controlling it and whether they're reliable to keep it up.

> > I have pre-installed Debian Wheezy onto your box. Once you power
> > it up and hook it up to the network, it should boot into Debian
> > Wheezy, the boot is finished once the LED has turned from purple
> > to solid blue.
> > 
> > You will be able to login via SSH using root/root.
> > 
> > The box was installed using the image "wheezy-sh4.dd" linked here:
> > 
> >> https://github.com/fuyuanli/nextvod-linux-manual/blob/master/doc/02.01.md
> > 
> > Original firmware can be found here:
> > 
> >> https://code.google.com/p/nexttv-mod/downloads/detail?name=U-boot_sourcecode.zip
> > 
> > And the original stlinux distribution is to be found here:
> > 
> >> http://archive.stlinux.com/stlinux/index.html
> > 
> 
> > 
> > Some stuff can be found here:
> > 
> >> https://github.com/OpenSH4
> >> https://github.com/dlintw/nextvod-tdt
> >> https://github.com/dlintw/sh4twbox-build-env
> >> https://github.com/dlintw/sh4twbox-multiboot
> > 
> > The kernel is here:
> > 
> >> https://github.com/dlintw/kernel-pdk7105
> > 
> > And I just found there is apparently a more modern kernel:
> > 
> >> https://github.com/dlintw/pdk7105-3.4
> 
> Ooh, did you send one to Sato-san too? (Or is he just cc'd?)

The 3.4 one looks incomplete and even more undocumented. It's not even
clear what version of the upstream kernel it's forked off of or how
they got the underlying ST support since STlinux didn't make it to 3.4
AFAIK.

> And there was more about the serial adapter but that boiled down to
> "Rich offered to mail me a cable" so I don't have a window open for
> that.
> 
> Info about where these boards _come_ from and so on would be nice.
> "Ask Adrian to mail you one" seems unlikely to scale.

Yes, I've had several ppl ask, and I couldn't find it on Yahoo
Auctions Taiwan anymore. Is it still possible to obtain them?

> And I already asked if there was an existing community of
> devs banging on these in China (seems like, since so much stuff is
> translated) that we could maybe talk to...
> 
> (It's a fun little board. Bit like the original linksys, only
> smaller and with video outputs. I look forward to powering it on.)
> 
> > This could be a good direction for future of arch/sh -- presumably all
> > the ST SoCs have a lot in common and could probably be a good first
> > target for supporting with device tree rather than legacy-style board
> > files full of platform devices.
> 
> Rich, I'll see if I can get you one of the SH7760 boards I'm working
> on at this contract, but it won't happen this month.

Great!

Rich