[Solved] Asus TB S

This is for any ARMv7 device that we do not officially support.

Re: Asus TB S

Postby TheSaint » Sun Aug 26, 2018 7:03 am

So the current situation is to be able to boot the kernel. I've done
Code: Select all
$ patch -p1 <board_tinkerboard/0036-auto-enable-ums-mode-when-TinkerBoard-is-connected-t.patch
$ patch -p1 <board_tinkerboard/0037-add-10ms-delay-after-re-enable-EMMC.patch
$ patch -p1 <board_tinkerboard/0039-fixed-enter-ums-mode-fail-sometimes.patch
$ patch -p1 <board_tinkerboard/0045-modify-UMS-name-of-uboot.patch
$ patch -p1 <board_tinkerboard/0049-added-timeout-when-force-entering-UMS-mode.patch
$ patch -p1 <board_tinkerboard/0050-USB-VID-PID.patch
$ patch -p1 <board_tinkerboard/100-tinker-s-eMMC-bootable.patch
$ patch -p1 <board_tinkerboard/101-u-boot-0002-rockchip-tinker-enable-rockchip-video-driver.patch

Which are almost all the Armbian patches and some small personal arrangement, but I think aren't influent.
So I suppose the u-boot would work with this configuration
Code: Select all
CONFIG_CREATE_ARCH_SYMLINK=y
CONFIG_ARM=y
CONFIG_SYS_ARCH="arm"
CONFIG_SYS_CPU="armv7"
CONFIG_SYS_SOC="rockchip"
CONFIG_SYS_VENDOR="rockchip"
CONFIG_SYS_BOARD="tinker_rk3288"
CONFIG_SYS_CONFIG_NAME="tinker_rk3288"
CONFIG_HAS_VBAR=y
CONFIG_HAS_THUMB2=y
CONFIG_ARM_ASM_UNIFIED=y
CONFIG_SYS_ARM_CACHE_CP15=y
CONFIG_SYS_ARM_MMU=y
CONFIG_CPU_V7A=y
CONFIG_SYS_ARM_ARCH=7
CONFIG_SYS_CACHE_SHIFT_6=y
CONFIG_SYS_CACHELINE_SIZE=64
CONFIG_SYS_THUMB_BUILD=y
CONFIG_SPL_SYS_THUMB_BUILD=y
CONFIG_ENABLE_ARM_SOC_BOOT0_HOOK=y
CONFIG_USE_ARCH_MEMCPY=y
CONFIG_SPL_USE_ARCH_MEMCPY=y
CONFIG_USE_ARCH_MEMSET=y
CONFIG_SPL_USE_ARCH_MEMSET=y
CONFIG_SPL_LDSCRIPT="arch/$(ARCH)/cpu/u-boot-spl.lds"
CONFIG_ARCH_ROCKCHIP=y
CONFIG_SYS_TEXT_BASE=0x00000000
CONFIG_SPL_LIBCOMMON_SUPPORT=y
CONFIG_SPL_LIBGENERIC_SUPPORT=y
CONFIG_SYS_MALLOC_F_LEN=0x2000
CONFIG_ROCKCHIP_RK3288=y
CONFIG_TPL_LDSCRIPT="arch/arm/mach-rockchip/rk3288/u-boot-tpl.lds"
CONFIG_TPL_TEXT_BASE=0xff704000
CONFIG_SPL_ROCKCHIP_BACK_TO_BROM=y
CONFIG_ROCKCHIP_BOOT_MODE_REG=0xff730094
CONFIG_ROCKCHIP_SPL_RESERVE_IRAM=0
CONFIG_ROCKCHIP_BROM_HELPER=y
CONFIG_SPL_SERIAL_SUPPORT=y
CONFIG_BOARD_SPECIFIC_OPTIONS=y
CONFIG_TARGET_TINKER_RK3288=y
CONFIG_SPL_DRIVERS_MISC_SUPPORT=y
CONFIG_ENV_SIZE=0x8000
CONFIG_ENV_OFFSET=0x3f8000
CONFIG_SPL_SYS_MALLOC_F_LEN=0x2000
CONFIG_SPL=y
CONFIG_DEBUG_UART_BASE=0xff690000
CONFIG_DEBUG_UART_CLOCK=24000000
CONFIG_IDENT_STRING=""
CONFIG_SPL_STACK_R_ADDR=0x80000
CONFIG_DEFAULT_DEVICE_TREE="rk3288-tinker"
CONFIG_SMBIOS_PRODUCT_NAME="tinker_rk3288"
CONFIG_DEBUG_UART=y
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_DISTRO_DEFAULTS=y
CONFIG_ENV_VARS_UBOOT_CONFIG=y
CONFIG_SYS_MALLOC_F=y
CONFIG_TPL_SYS_MALLOC_F_LEN=0x2000
CONFIG_EXPERT=y
CONFIG_SYS_MALLOC_CLEAR_ON_INIT=y
CONFIG_IMAGE_FORMAT_LEGACY=y
CONFIG_SYS_EXTRA_OPTIONS=""
CONFIG_ARCH_FIXUP_FDT_MEMORY=y
CONFIG_BOOTSTAGE_RECORD_COUNT=30
CONFIG_SPL_BOOTSTAGE_RECORD_COUNT=5
CONFIG_BOOTSTAGE_STASH_ADDR=0
CONFIG_BOOTSTAGE_STASH_SIZE=0x1000
CONFIG_SD_BOOT=y
CONFIG_BOOTDELAY=2
CONFIG_USE_BOOTCOMMAND=y
CONFIG_BOOTCOMMAND="run distro_bootcmd"
CONFIG_MENU=y
CONFIG_LOGLEVEL=4
CONFIG_SPL_LOGLEVEL=4
CONFIG_SILENT_CONSOLE=y
CONFIG_SILENT_CONSOLE_UPDATE_ON_SET=y
CONFIG_CONSOLE_MUX=y
CONFIG_SYS_CONSOLE_IS_IN_ENV=y
CONFIG_SUPPORT_RAW_INITRD=y
CONFIG_DEFAULT_FDT_FILE="rk3288-tinker.dtb"
CONFIG_BOARD_LATE_INIT=y
CONFIG_DISPLAY_BOARDINFO=y
CONFIG_DISPLAY_BOARDINFO_LATE=y
CONFIG_HASH=y
CONFIG_SUPPORT_SPL=y
CONFIG_SPL_FRAMEWORK=y
CONFIG_SPL_BOARD_INIT=y
CONFIG_SPL_RAW_IMAGE_SUPPORT=y
CONFIG_SPL_LEGACY_IMAGE_SUPPORT=y
CONFIG_SPL_SYS_MALLOC_SIMPLE=y
CONFIG_SPL_STACK_R=y
CONFIG_SPL_STACK_R_MALLOC_SIMPLE_LEN=0x2000
CONFIG_SPL_I2C_SUPPORT=y
CONFIG_SPL_PAYLOAD="u-boot.bin"
CONFIG_CMDLINE=y
CONFIG_HUSH_PARSER=y
CONFIG_CMDLINE_EDITING=y
CONFIG_AUTO_COMPLETE=y
CONFIG_SYS_LONGHELP=y
CONFIG_SYS_PROMPT="=> "
CONFIG_AUTOBOOT=y
CONFIG_CMD_BDI=y
CONFIG_CMD_CONSOLE=y
CONFIG_CMD_BOOTD=y
CONFIG_CMD_BOOTM=y
CONFIG_CMD_BOOTZ=y
CONFIG_CMD_BOOTEFI=y
CONFIG_CMD_BOOTMENU=y
CONFIG_CMD_ELF=y
CONFIG_CMD_FDT=y
CONFIG_CMD_GO=y
CONFIG_CMD_RUN=y
CONFIG_CMD_IMI=y
CONFIG_CMD_XIMG=y
CONFIG_CMD_EXPORTENV=y
CONFIG_CMD_IMPORTENV=y
CONFIG_CMD_EDITENV=y
CONFIG_CMD_SAVEENV=y
CONFIG_CMD_ENV_EXISTS=y
CONFIG_CMD_CRC32=y
CONFIG_CMD_MEMORY=y
CONFIG_CMD_DM=y
CONFIG_CMD_FASTBOOT=y
CONFIG_CMD_FLASH=y
CONFIG_CMD_GPIO=y
CONFIG_CMD_GPT=y
CONFIG_RANDOM_UUID=y
CONFIG_CMD_I2C=y
CONFIG_CMD_LOADB=y
CONFIG_CMD_LOADS=y
CONFIG_CMD_MMC=y
CONFIG_CMD_PART=y
CONFIG_CMD_SF=y
CONFIG_CMD_SPI=y
CONFIG_CMD_USB=y
CONFIG_CMD_ROCKUSB=y
CONFIG_CMD_ECHO=y
CONFIG_CMD_ITEST=y
CONFIG_CMD_SOURCE=y
CONFIG_CMD_BLOCK_CACHE=y
CONFIG_CMD_CACHE=y
CONFIG_CMD_TIME=y
CONFIG_CMD_MISC=y
CONFIG_CMD_PMIC=y
CONFIG_CMD_REGULATOR=y
CONFIG_CMD_EXT2=y
CONFIG_CMD_EXT4=y
CONFIG_CMD_FAT=y
CONFIG_CMD_FS_GENERIC=y
CONFIG_MTDIDS_DEFAULT=""
CONFIG_MTDPARTS_DEFAULT=""
CONFIG_PARTITIONS=y
CONFIG_DOS_PARTITION=y
CONFIG_ISO_PARTITION=y
CONFIG_EFI_PARTITION=y
CONFIG_EFI_PARTITION_ENTRIES_NUMBERS=128
CONFIG_EFI_PARTITION_ENTRIES_OFF=0
CONFIG_PARTITION_UUIDS=y
CONFIG_SPL_PARTITION_UUIDS=y
CONFIG_SUPPORT_OF_CONTROL=y
CONFIG_DTC=y
CONFIG_OF_CONTROL=y
CONFIG_SPL_OF_CONTROL=y
CONFIG_OF_SEPARATE=y
CONFIG_OF_SPL_REMOVE_PROPS="pinctrl-0 pinctrl-names clock-names interrupt-parent assigned-clocks assigned-clock-rates assigned-clock-parents"
CONFIG_MKIMAGE_DTC_PATH="dtc"
CONFIG_ENV_IS_IN_MMC=y
CONFIG_DM=y
CONFIG_SPL_DM=y
CONFIG_DM_WARN=y
CONFIG_DM_DEVICE_REMOVE=y
CONFIG_DM_STDIO=y
CONFIG_DM_SEQ_ALIAS=y
CONFIG_REGMAP=y
CONFIG_SPL_REGMAP=y
CONFIG_SYSCON=y
CONFIG_SPL_SYSCON=y
CONFIG_SIMPLE_BUS=y
CONFIG_OF_TRANSLATE=y
CONFIG_DM_DEV_READ_INLINE=y
CONFIG_ADC=y
CONFIG_SARADC_ROCKCHIP=y
CONFIG_BLK=y
CONFIG_HAVE_BLOCK_DEVICE=y
CONFIG_SPL_BLK=y
CONFIG_BLOCK_CACHE=y
CONFIG_CLK=y
CONFIG_SPL_CLK=y
CONFIG_FASTBOOT=y
CONFIG_USB_FUNCTION_FASTBOOT=y
CONFIG_FASTBOOT_BUF_ADDR=0x800800
CONFIG_FASTBOOT_BUF_SIZE=0x8000000
CONFIG_FASTBOOT_USB_DEV=0
CONFIG_FASTBOOT_FLASH=y
CONFIG_FASTBOOT_FLASH_MMC=y
CONFIG_FASTBOOT_FLASH_MMC_DEV=0
CONFIG_FASTBOOT_GPT_NAME="gpt"
CONFIG_FASTBOOT_MBR_NAME="mbr"
CONFIG_FASTBOOT_CMD_OEM_FORMAT=y
CONFIG_DM_GPIO=y
CONFIG_ROCKCHIP_GPIO=y
CONFIG_DM_I2C=y
CONFIG_SYS_I2C_ROCKCHIP=y
CONFIG_MISC=y
CONFIG_I2C_EEPROM=y
CONFIG_ZYNQ_GEM_I2C_MAC_OFFSET=0x0
CONFIG_SYS_I2C_EEPROM_ADDR=0
CONFIG_SYS_I2C_EEPROM_BUS=0
CONFIG_SYS_EEPROM_SIZE=256
CONFIG_SYS_EEPROM_PAGE_WRITE_BITS=0
CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS=0
CONFIG_SYS_I2C_EEPROM_ADDR_LEN=1
CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW=0
CONFIG_MMC=y
CONFIG_MMC_WRITE=y
CONFIG_DM_MMC=y
CONFIG_SPL_DM_MMC=y
CONFIG_MMC_QUIRKS=y
CONFIG_MMC_HW_PARTITIONING=y
CONFIG_MMC_VERBOSE=y
CONFIG_MMC_DW=y
CONFIG_MMC_DW_ROCKCHIP=y
CONFIG_DM_SPI_FLASH=y
CONFIG_DM_ETH=y
CONFIG_PINCTRL=y
CONFIG_PINCTRL_FULL=y
CONFIG_PINCTRL_GENERIC=y
CONFIG_PINMUX=y
CONFIG_SPL_PINCTRL=y
CONFIG_PINCTRL_ROCKCHIP_RK3288=y
CONFIG_DM_PMIC=y
CONFIG_PMIC_CHILDREN=y
CONFIG_SPL_PMIC_CHILDREN=y
CONFIG_PMIC_RK8XX=y
CONFIG_DM_REGULATOR=y
CONFIG_DM_REGULATOR_FIXED=y
CONFIG_REGULATOR_RK8XX=y
CONFIG_DM_PWM=y
CONFIG_PWM_ROCKCHIP=y
CONFIG_RAM=y
CONFIG_SPL_RAM=y
CONFIG_BAUDRATE=115200
CONFIG_REQUIRE_SERIAL_CONSOLE=y
CONFIG_SERIAL_PRESENT=y
CONFIG_SPL_SERIAL_PRESENT=y
CONFIG_DM_SERIAL=y
CONFIG_SPL_DM_SERIAL=y
CONFIG_DEBUG_UART_NS16550=y
CONFIG_DEBUG_UART_SHIFT=2
CONFIG_SYS_NS16550=y
CONFIG_SPI=y
CONFIG_DM_SPI=y
CONFIG_SYSRESET=y
CONFIG_USB=y
CONFIG_DM_USB=y
CONFIG_USB_HOST=y
CONFIG_USB_DWC2=y
CONFIG_USB_DWC2_BUFFER_SIZE=64
CONFIG_ROCKCHIP_USB2_PHY=y
CONFIG_USB_STORAGE=y
CONFIG_USB_GADGET=y
CONFIG_USB_GADGET_MANUFACTURER="ASUS"
CONFIG_USB_GADGET_VENDOR_NUM=0x0b05
CONFIG_USB_GADGET_PRODUCT_NUM=0x7820
CONFIG_USB_GADGET_DWC2_OTG=y
CONFIG_USB_GADGET_VBUS_DRAW=2
CONFIG_USB_GADGET_DUALSPEED=y
CONFIG_USB_GADGET_DOWNLOAD=y
CONFIG_USB_FUNCTION_MASS_STORAGE=y
CONFIG_USB_FUNCTION_ROCKUSB=y
CONFIG_DM_VIDEO=y
CONFIG_BACKLIGHT_PWM=y
CONFIG_VIDEO_BPP8=y
CONFIG_VIDEO_BPP16=y
CONFIG_VIDEO_BPP32=y
CONFIG_VIDEO_ANSI=y
CONFIG_CONSOLE_NORMAL=y
CONFIG_SYS_WHITE_ON_BLACK=y
CONFIG_I2C_EDID=y
CONFIG_DISPLAY=y
CONFIG_VIDEO_ROCKCHIP=y
CONFIG_VIDEO_ROCKCHIP_MAX_XRES=1920
CONFIG_VIDEO_ROCKCHIP_MAX_YRES=1080
CONFIG_DISPLAY_ROCKCHIP_HDMI=y
CONFIG_CONSOLE_SCROLL_LINES=10
CONFIG_VIDEO_DW_HDMI=y
CONFIG_FS_EXT4=y
CONFIG_FS_FAT=y
CONFIG_FAT_WRITE=y
CONFIG_FS_FAT_MAX_CLUSTSIZE=65536
CONFIG_HAVE_PRIVATE_LIBGCC=y
CONFIG_LIB_UUID=y
CONFIG_PRINTF=y
CONFIG_SPL_PRINTF=y
CONFIG_SPRINTF=y
CONFIG_SPL_SPRINTF=y
CONFIG_STRTO=y
CONFIG_SPL_STRTO=y
CONFIG_IMAGE_SPARSE=y
CONFIG_IMAGE_SPARSE_FILLBUF_SIZE=0x80000
CONFIG_USE_PRIVATE_LIBGCC=y
CONFIG_SYS_HZ=1000
CONFIG_USE_TINY_PRINTF=y
CONFIG_LIB_RAND=y
CONFIG_CMD_DHRYSTONE=y
CONFIG_ERRNO_STR=y
CONFIG_OF_LIBFDT=y
CONFIG_SPL_OF_LIBFDT=y
CONFIG_GENERATE_SMBIOS_TABLE=y
CONFIG_SMBIOS_MANUFACTURER="rockchip"
CONFIG_EFI_LOADER=y
CONFIG_OPTEE_LOAD_ADDR=0x00000000

About me the u-boot is good enough like this, including your boot.scr ;). There's a little problem that u-boot doesn't stop during the autoboot delay. Correction was my oversight
I presume that the similar patches should go to the kernel and then it will stop to joggle the mmc speed.
Last edited by TheSaint on Mon Aug 27, 2018 2:50 am, edited 1 time in total.
TheSaint
 
Posts: 345
Joined: Mon Jul 23, 2018 7:57 am

Re: Asus TB S

Postby summers » Sun Aug 26, 2018 7:41 am

Actually its encouraging in some ways. the rockchip sdio drive detects 3 devices:
Code: Select all
 [    4.108481] dwmmc_rockchip ff0c0000.dwmmc: DW MMC controller at irq 30,32 bit host data width,256 deep fifo
[    4.177444] dwmmc_rockchip ff0d0000.dwmmc: DW MMC controller at irq 31,32 bit host data width,256 deep fifo
[    4.269654] dwmmc_rockchip ff0f0000.dwmmc: DW MMC controller at irq 32,32 bit host data width,256 deep fifo

So thats the sd card, the wi-fi and the eMMC.

It detects two mmc devices:
Code: Select all
[    4.221057] mmc0: new high speed SDHC card at address 0007
[    4.317208] mmc1: new high speed SDIO card at address 0001


So I'd be tempted to try
Code: Select all
sudo fdisk /dev/mmcblk0
sudo fdisk /dev/mmcblk1
sudo fdisk /dev/mmcblk2

The first code we expect to work (so e.g. you can "p"rint the partition table. The last code we expect to fail (no device 2), but what does the second do?

On u-boot, pity not more was seen. I guess "mmc scan" didn't show anything else. If I had to guess what it may be its the file:
Code: Select all
include/configs/tinker_rk3288.h

It has the code
Code: Select all
#define BOOT_TARGET_DEVICES(func) \
   func(MMC, mmc, 1) \
   func(USB, usb, 0) \
   func(PXE, pxe, na) \
   func(DHCP, dchp, na)

And that gives what devices to scan. Now one of your patches removed this. I didn't work out what it was doing instead. I think its what u-boot scans at boot.

Now I didn't want to just remove this, as the above is the way that most board are set up on mainline u-boot. ANyway I'll dig some more, and compare your config to my own ...
summers
 
Posts: 868
Joined: Sat Sep 06, 2014 12:56 pm

Re: Asus TB S

Postby summers » Sun Aug 26, 2018 9:25 am

OK this is the patch that does auto ums https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-rockchip/board_tinkerboard/0036-auto-enable-ums-mode-when-TinkerBoard-is-connected-t.patch

I'm minded, not to apply - it says that if plugged into a PC go into UMS mode. Now I think that means that the TBS doesn't boot. Now to my mind that is limiting. e.g. a possible user case, is TBS powered off a PC, and at linux powerup, it starts a USB gadget, and enables things like ethernet and serial to the host PC. This is how I run my pocketbeagle btw - and for that machine other that uart its the only way in!

However that patch says you can also have the same effect with the u-boot command "ums 1 mmc 0", so entering that at a u-boot prompt should give UMS mode.

Other interesting thing that patch does, is it shows how to read the board and the revision from the device. This can distinguish between TB and TBS. It would make sense for this to be in u-boot mainstream -a as it means we could do a single u-boot.bin that works for both TB and TBS, and that u-boot changes the dtb dependent on the hardware. This is how the beagle family work btw ...
summers
 
Posts: 868
Joined: Sat Sep 06, 2014 12:56 pm

Re: Asus TB S

Postby summers » Sun Aug 26, 2018 12:08 pm

OK the only significant uboot difference I could see was in : include/configs/tinker_rk3288.h
Code: Select all
#define BOOT_TARGET_DEVICES(func) \
   func(MMC, mmc, 1) \
   func(USB, usb, 0) \
   func(PXE, pxe, na) \
   func(DHCP, dchp, na)

thee armian patch removed this, which means its revers to the file: include/configs/rockchip-common.h
Code: Select all
/* First try to boot from SD (index 0), then eMMC (index 1) */
#if CONFIG_IS_ENABLED(CMD_MMC)
   #define BOOT_TARGET_MMC(func) \
      func(MMC, mmc, 0) \
      func(MMC, mmc, 1)
#else
   #define BOOT_TARGET_MMC(func)
#endif

#if CONFIG_IS_ENABLED(CMD_USB)
   #define BOOT_TARGET_USB(func) func(USB, usb, 0)
#else
   #define BOOT_TARGET_USB(func)
#endif

#if CONFIG_IS_ENABLED(CMD_PXE)
   #define BOOT_TARGET_PXE(func) func(PXE, pxe, na)
#else
   #define BOOT_TARGET_PXE(func)
#endif

#if CONFIG_IS_ENABLED(CMD_DHCP)
   #define BOOT_TARGET_DHCP(func) func(DHCP, dhcp, na)
#else
   #define BOOT_TARGET_DHCP(func)
#endif

#define BOOT_TARGET_DEVICES(func) \
   BOOT_TARGET_MMC(func) \
   BOOT_TARGET_USB(func) \
   BOOT_TARGET_PXE(func) \
   BOOT_TARGET_DHCP(func)


So the important bit is doing both mmc 0 and mmc 1 - I'll do that by hand as proof of concept. Not clear to me which way is best ...

EDIT: OK I've redone the u-boot image only to explicitly scan both eMMC and sd here: http://davidjohnsummers.uk/TBS5.tar.gz - so you'll just need to do the u-boot image. The dtb file is the same as before.

I *think* my u-boot set up is *very* close to the armian patched version btw, so am hopeful it works ...

Oh yes did you try wi-fi with the latest dtb file? That should have been enabled ....
summers
 
Posts: 868
Joined: Sat Sep 06, 2014 12:56 pm

Re: Asus TB S

Postby TheSaint » Mon Aug 27, 2018 3:38 am

summers wrote:OK this is the patch that does auto ums

I've tried that alone, but it didn't suffice. I might go back to try every patch one by one, to help out to find which suffice.

summers wrote:I'm minded, not to apply - it says that if plugged into a PC go into UMS mode. Now I think that means that the TBS doesn't boot.

That's it. It starts the UMS mode, so the eMMC is just a common block device. From my point of view is enough and one may write correction to it.

summers wrote:Now to my mind that is limiting

The huge problem is TBS power hunger. So for certain USB PC might supply only 500 mA, which will cause bad functioning from TBS side. That should be the reason why they don't accept to start the kernel while powered by a PC.

summers wrote:However that patch says you can also have the same effect with the u-boot command "ums 1 mmc 0", so entering that at a u-boot prompt should give UMS mode.


Not that daily usage, because it will need a serial port engaged and stop the u-boot. I think it isn't an ordinary case, but it would become a bit complicated.
I've tried that way, when I set the TBS4 guideline. Then when plugged to PC it tries to boot, but at certain point it switches itself off.
summers wrote:This can distinguish between TB and TBS.

Good option. I'd suggest to keep an eye to those patches, there's a lot of truth in there to make tinker Board working. The deepest difference is that we are ahead to run newer programs and the TB peoples prefer/opt to debian living style.

summers wrote:EDIT: OK I've redone the u-boot image only to explicitly scan both eMMC

I wish you that you've done the right one. Mine are just less pondered solution, such try&fail. Anyway I realize the patches giving an expected result. I just omitted those referred to HDMI, because I won't expect to use the TB connected to a TV-set.

summers wrote:Oh yes did you try wi-fi with the latest dtb file?

I'll go back to that thread once I'll see the kernel booting fully and I'll be able to operate on the modules.
There still one think I hardly understand. Is the u-boot able to fix all the thing that the kernel needs. What about the mmc speed joggling ?

I gone to try to compile my own kernel, but I didn't find much related to tinker or rockchip in the linux-4.18, then I went to armian site to get their config file. Anyway there still are differences, it seems that certain files are not there anymore.
I think that the stock kernel cannot handle eMMC correctly, like u-boot with patches doing.
TheSaint
 
Posts: 345
Joined: Mon Jul 23, 2018 7:57 am

Re: Asus TB S

Postby summers » Mon Aug 27, 2018 9:39 am

If you mean the problem here: https://archlinuxarm.org/forum/viewtopic.php?f=44&t=12952&start=100#p59184, I think what happened in that u-boot passed the root id for the eMMC, but that the kernel didn't manage to find the eMMC. So the mmc0 error seem to be when it accessing the sd card slot. Was there a sd card plugged in?

My guess is that your u-boot and my rk3288-tinkerS.dtb would boot, and stand a reasonable chance of mounting the eMMC. Problem is that your u-boot will look for rk3288-tinker.dtb - so you either need to interrupt uboot and point it to rk3288-tinkerS.dtb. Or rename the device tree blob. This said though we should probably first ensure we can access the eMMC, even when booted in the sd card.

Hand crafted kernel used to be the thing to do on arm boards before the device tree came along. Problem was the kernel needed to be configured for exactly where all hardware is. E.g. on your TBS, the sdio has an eMMC, and sd card, and wi-fi all on that bus, and there is no way the kernel would know that. The RK808 on the i2c also would be a bit hidden.

The advent of device trees changed all that, it took all the description of hardware into that one file. It makes the kernel far easier, all it has to do is check the file to know what to bring up where. It means these days kernels have gone back to general kernels for many machines, that just load the modules that they need. It really is more sensible now.

Anyway best of luck in crafting your own kernel.
summers
 
Posts: 868
Joined: Sat Sep 06, 2014 12:56 pm

Re: Asus TB S

Postby TheSaint » Mon Aug 27, 2018 2:32 pm

summers wrote:My guess is that your u-boot and my rk3288-tinkerS.dtb would boot, and stand a reasonable chance of mounting the eMMC

This time we got farther and we reached the login. But still we have the annoyance of mmc speed joggling. Perhaps the normal login won't have this visible, it is just the kernel logging on UART2. Anyway is a bit of CPU wastage.
Code: Select all
[  OK  ] Reached target Graphical Interface.
[   12.528235] mmc_host mmc0: Bus speed (slot 0) = 187500Hz (slot req 100000Hz, actual 93750HZ div = 1)

Arch Linux 4.17.11-1-ARCH (ttyS2)

alarm login: [   12.887112] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[   12.928352] mmc_host mmc0: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0)
[   12.969587] mmc_host mmc0: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0)
[   13.010861] mmc_host mmc0: Bus speed (slot 0) = 187500Hz (slot req 100000Hz, actual 93750HZ div = 1)

I've tried to find where that phrase is written but I didn't get any result.

This time I used this config
Code: Select all
CONFIG_CREATE_ARCH_SYMLINK=y
CONFIG_ARM=y
CONFIG_SYS_ARCH="arm"
CONFIG_SYS_CPU="armv7"
CONFIG_SYS_SOC="rockchip"
CONFIG_SYS_VENDOR="rockchip"
CONFIG_SYS_BOARD="tinker_rk3288"
CONFIG_SYS_CONFIG_NAME="tinker_rk3288"
CONFIG_HAS_VBAR=y
CONFIG_HAS_THUMB2=y
CONFIG_ARM_ASM_UNIFIED=y
CONFIG_SYS_ARM_CACHE_CP15=y
CONFIG_SYS_ARM_MMU=y
CONFIG_CPU_V7A=y
CONFIG_SYS_ARM_ARCH=7
CONFIG_SYS_CACHE_SHIFT_6=y
CONFIG_SYS_CACHELINE_SIZE=64
CONFIG_SYS_THUMB_BUILD=y
CONFIG_SPL_SYS_THUMB_BUILD=y
CONFIG_ENABLE_ARM_SOC_BOOT0_HOOK=y
CONFIG_USE_ARCH_MEMCPY=y
CONFIG_SPL_USE_ARCH_MEMCPY=y
CONFIG_USE_ARCH_MEMSET=y
CONFIG_SPL_USE_ARCH_MEMSET=y
CONFIG_SPL_LDSCRIPT="arch/$(ARCH)/cpu/u-boot-spl.lds"
CONFIG_ARCH_ROCKCHIP=y
CONFIG_SYS_TEXT_BASE=0x00000000
CONFIG_SPL_LIBCOMMON_SUPPORT=y
CONFIG_SPL_LIBGENERIC_SUPPORT=y
CONFIG_SYS_MALLOC_F_LEN=0x2000
CONFIG_ROCKCHIP_RK3288=y
CONFIG_TPL_LDSCRIPT="arch/arm/mach-rockchip/rk3288/u-boot-tpl.lds"
CONFIG_TPL_TEXT_BASE=0xff704000
CONFIG_SPL_ROCKCHIP_BACK_TO_BROM=y
CONFIG_ROCKCHIP_BOOT_MODE_REG=0xff730094
CONFIG_ROCKCHIP_SPL_RESERVE_IRAM=0
CONFIG_ROCKCHIP_BROM_HELPER=y
CONFIG_SPL_SERIAL_SUPPORT=y
CONFIG_BOARD_SPECIFIC_OPTIONS=y
CONFIG_TARGET_TINKER_RK3288=y
CONFIG_SPL_DRIVERS_MISC_SUPPORT=y
CONFIG_ENV_SIZE=0x8000
CONFIG_ENV_OFFSET=0x3f8000
CONFIG_SPL_SYS_MALLOC_F_LEN=0x2000
CONFIG_SPL=y
CONFIG_DEBUG_UART_BASE=0xff690000
CONFIG_DEBUG_UART_CLOCK=24000000
CONFIG_IDENT_STRING=""
CONFIG_SPL_STACK_R_ADDR=0x80000
CONFIG_DEFAULT_DEVICE_TREE="rk3288-tinker"
CONFIG_SMBIOS_PRODUCT_NAME="tinker_rk3288"
CONFIG_DEBUG_UART=y
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_DISTRO_DEFAULTS=y
CONFIG_ENV_VARS_UBOOT_CONFIG=y
CONFIG_SYS_MALLOC_F=y
CONFIG_TPL_SYS_MALLOC_F_LEN=0x2000
CONFIG_EXPERT=y
CONFIG_SYS_MALLOC_CLEAR_ON_INIT=y
CONFIG_IMAGE_FORMAT_LEGACY=y
CONFIG_SYS_EXTRA_OPTIONS=""
CONFIG_ARCH_FIXUP_FDT_MEMORY=y
CONFIG_BOOTSTAGE_RECORD_COUNT=30
CONFIG_SPL_BOOTSTAGE_RECORD_COUNT=5
CONFIG_BOOTSTAGE_STASH_ADDR=0
CONFIG_BOOTSTAGE_STASH_SIZE=0x1000
CONFIG_BOOTDELAY=5
CONFIG_USE_BOOTCOMMAND=y
CONFIG_BOOTCOMMAND="run distro_bootcmd"
CONFIG_MENU=y
CONFIG_LOGLEVEL=4
CONFIG_SPL_LOGLEVEL=4
CONFIG_SILENT_CONSOLE=y
CONFIG_SILENT_CONSOLE_UPDATE_ON_SET=y
CONFIG_CONSOLE_MUX=y
CONFIG_SYS_CONSOLE_IS_IN_ENV=y
CONFIG_SUPPORT_RAW_INITRD=y
CONFIG_DEFAULT_FDT_FILE="rk3288-tinkerS.dtb"
CONFIG_BOARD_LATE_INIT=y
CONFIG_DISPLAY_BOARDINFO=y
CONFIG_DISPLAY_BOARDINFO_LATE=y
CONFIG_HASH=y
CONFIG_SUPPORT_SPL=y
CONFIG_SPL_FRAMEWORK=y
CONFIG_SPL_BOARD_INIT=y
CONFIG_SPL_RAW_IMAGE_SUPPORT=y
CONFIG_SPL_LEGACY_IMAGE_SUPPORT=y
CONFIG_SPL_SYS_MALLOC_SIMPLE=y
CONFIG_SPL_STACK_R=y
CONFIG_SPL_STACK_R_MALLOC_SIMPLE_LEN=0x2000
CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR=y
CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR=0x4000
CONFIG_SPL_I2C_SUPPORT=y
CONFIG_SPL_PAYLOAD="u-boot.bin"
CONFIG_CMDLINE=y
CONFIG_HUSH_PARSER=y
CONFIG_CMDLINE_EDITING=y
CONFIG_AUTO_COMPLETE=y
CONFIG_SYS_LONGHELP=y
CONFIG_SYS_PROMPT="=> "
CONFIG_AUTOBOOT=y
CONFIG_CMD_BDI=y
CONFIG_CMD_CONSOLE=y
CONFIG_CMD_BOOTD=y
CONFIG_CMD_BOOTM=y
CONFIG_CMD_BOOTZ=y
CONFIG_CMD_BOOTEFI=y
CONFIG_CMD_BOOTEFI_HELLO_COMPILE=y
CONFIG_CMD_ELF=y
CONFIG_CMD_FDT=y
CONFIG_CMD_GO=y
CONFIG_CMD_RUN=y
CONFIG_CMD_IMI=y
CONFIG_CMD_XIMG=y
CONFIG_CMD_EXPORTENV=y
CONFIG_CMD_IMPORTENV=y
CONFIG_CMD_EDITENV=y
CONFIG_CMD_SAVEENV=y
CONFIG_CMD_ENV_EXISTS=y
CONFIG_CMD_CRC32=y
CONFIG_CMD_MEMORY=y
CONFIG_CMD_DM=y
CONFIG_CMD_FASTBOOT=y
CONFIG_CMD_FLASH=y
CONFIG_CMD_GPIO=y
CONFIG_CMD_GPT=y
CONFIG_RANDOM_UUID=y
CONFIG_CMD_I2C=y
CONFIG_CMD_LOADB=y
CONFIG_CMD_LOADS=y
CONFIG_CMD_MMC=y
CONFIG_CMD_PART=y
CONFIG_CMD_SF=y
CONFIG_CMD_SPI=y
CONFIG_CMD_USB=y
CONFIG_CMD_ROCKUSB=y
CONFIG_CMD_ECHO=y
CONFIG_CMD_ITEST=y
CONFIG_CMD_SOURCE=y
CONFIG_CMD_NET=y
CONFIG_CMD_BOOTP=y
CONFIG_CMD_DHCP=y
CONFIG_BOOTP_BOOTPATH=y
CONFIG_BOOTP_DNS=y
CONFIG_BOOTP_GATEWAY=y
CONFIG_BOOTP_HOSTNAME=y
CONFIG_BOOTP_SUBNETMASK=y
CONFIG_BOOTP_PXE=y
CONFIG_BOOTP_PXE_CLIENTARCH=0x15
CONFIG_BOOTP_VCI_STRING="U-Boot.armv7"
CONFIG_CMD_TFTPBOOT=y
CONFIG_NET_TFTP_VARS=y
CONFIG_CMD_NFS=y
CONFIG_CMD_MII=y
CONFIG_CMD_PING=y
CONFIG_CMD_PXE=y
CONFIG_CMD_BLOCK_CACHE=y
CONFIG_CMD_CACHE=y
CONFIG_CMD_TIME=y
CONFIG_CMD_MISC=y
CONFIG_CMD_PMIC=y
CONFIG_CMD_REGULATOR=y
CONFIG_CMD_EXT2=y
CONFIG_CMD_EXT4=y
CONFIG_CMD_FAT=y
CONFIG_CMD_FS_GENERIC=y
CONFIG_MTDIDS_DEFAULT=""
CONFIG_MTDPARTS_DEFAULT=""
CONFIG_PARTITIONS=y
CONFIG_DOS_PARTITION=y
CONFIG_ISO_PARTITION=y
CONFIG_EFI_PARTITION=y
CONFIG_EFI_PARTITION_ENTRIES_NUMBERS=128
CONFIG_EFI_PARTITION_ENTRIES_OFF=0
CONFIG_PARTITION_UUIDS=y
CONFIG_SPL_PARTITION_UUIDS=y
CONFIG_SUPPORT_OF_CONTROL=y
CONFIG_DTC=y
CONFIG_OF_CONTROL=y
CONFIG_SPL_OF_CONTROL=y
CONFIG_OF_SEPARATE=y
CONFIG_OF_SPL_REMOVE_PROPS="pinctrl-0 pinctrl-names clock-names interrupt-parent assigned-clocks assigned-clock-rates assigned-clock-parents"
CONFIG_MKIMAGE_DTC_PATH="dtc"
CONFIG_ENV_IS_IN_MMC=y
CONFIG_NET=y
CONFIG_DM=y
CONFIG_SPL_DM=y
CONFIG_DM_WARN=y
CONFIG_DM_DEVICE_REMOVE=y
CONFIG_DM_STDIO=y
CONFIG_DM_SEQ_ALIAS=y
CONFIG_REGMAP=y
CONFIG_SPL_REGMAP=y
CONFIG_SYSCON=y
CONFIG_SPL_SYSCON=y
CONFIG_SIMPLE_BUS=y
CONFIG_OF_TRANSLATE=y
CONFIG_DM_DEV_READ_INLINE=y
CONFIG_ADC=y
CONFIG_SARADC_ROCKCHIP=y
CONFIG_BLK=y
CONFIG_HAVE_BLOCK_DEVICE=y
CONFIG_SPL_BLK=y
CONFIG_BLOCK_CACHE=y
CONFIG_CLK=y
CONFIG_SPL_CLK=y
CONFIG_FASTBOOT=y
CONFIG_USB_FUNCTION_FASTBOOT=y
CONFIG_FASTBOOT_BUF_ADDR=0x800800
CONFIG_FASTBOOT_BUF_SIZE=0x8000000
CONFIG_FASTBOOT_USB_DEV=0
CONFIG_FASTBOOT_FLASH=y
CONFIG_FASTBOOT_FLASH_MMC=y
CONFIG_FASTBOOT_FLASH_MMC_DEV=0
CONFIG_FASTBOOT_GPT_NAME="gpt"
CONFIG_FASTBOOT_MBR_NAME="mbr"
CONFIG_FASTBOOT_CMD_OEM_FORMAT=y
CONFIG_DM_GPIO=y
CONFIG_ROCKCHIP_GPIO=y
CONFIG_DM_I2C=y
CONFIG_SYS_I2C_ROCKCHIP=y
CONFIG_MISC=y
CONFIG_I2C_EEPROM=y
CONFIG_ZYNQ_GEM_I2C_MAC_OFFSET=0x0
CONFIG_SYS_I2C_EEPROM_ADDR=0
CONFIG_SYS_I2C_EEPROM_BUS=0
CONFIG_SYS_EEPROM_SIZE=256
CONFIG_SYS_EEPROM_PAGE_WRITE_BITS=0
CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS=0
CONFIG_SYS_I2C_EEPROM_ADDR_LEN=1
CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW=0
CONFIG_MMC=y
CONFIG_MMC_WRITE=y
CONFIG_DM_MMC=y
CONFIG_SPL_DM_MMC=y
CONFIG_MMC_QUIRKS=y
CONFIG_MMC_HW_PARTITIONING=y
CONFIG_MMC_VERBOSE=y
CONFIG_MMC_DW=y
CONFIG_MMC_DW_ROCKCHIP=y
CONFIG_DM_SPI_FLASH=y
CONFIG_PHYLIB=y
CONFIG_DM_ETH=y
CONFIG_NETDEVICES=y
CONFIG_ETH_DESIGNWARE=y
CONFIG_GMAC_ROCKCHIP=y
CONFIG_PINCTRL=y
CONFIG_PINCTRL_FULL=y
CONFIG_PINCTRL_GENERIC=y
CONFIG_PINMUX=y
CONFIG_SPL_PINCTRL=y
CONFIG_PINCTRL_ROCKCHIP_RK3288=y
CONFIG_DM_PMIC=y
CONFIG_PMIC_CHILDREN=y
CONFIG_SPL_PMIC_CHILDREN=y
CONFIG_PMIC_RK8XX=y
CONFIG_DM_REGULATOR=y
CONFIG_DM_REGULATOR_FIXED=y
CONFIG_REGULATOR_RK8XX=y
CONFIG_DM_PWM=y
CONFIG_PWM_ROCKCHIP=y
CONFIG_RAM=y
CONFIG_SPL_RAM=y
CONFIG_BAUDRATE=115200
CONFIG_REQUIRE_SERIAL_CONSOLE=y
CONFIG_SERIAL_PRESENT=y
CONFIG_SPL_SERIAL_PRESENT=y
CONFIG_DM_SERIAL=y
CONFIG_SPL_DM_SERIAL=y
CONFIG_DEBUG_UART_NS16550=y
CONFIG_DEBUG_UART_SHIFT=2
CONFIG_SYS_NS16550=y
CONFIG_SPI=y
CONFIG_DM_SPI=y
CONFIG_SYSRESET=y
CONFIG_USB=y
CONFIG_DM_USB=y
CONFIG_USB_HOST=y
CONFIG_USB_DWC2=y
CONFIG_USB_DWC2_BUFFER_SIZE=64
CONFIG_ROCKCHIP_USB2_PHY=y
CONFIG_USB_STORAGE=y
CONFIG_USB_GADGET=y
CONFIG_USB_GADGET_MANUFACTURER="ASUS"
CONFIG_USB_GADGET_VENDOR_NUM=0x0b05
CONFIG_USB_GADGET_PRODUCT_NUM=0x7820
CONFIG_USB_GADGET_DWC2_OTG=y
CONFIG_USB_GADGET_VBUS_DRAW=2
CONFIG_USB_GADGET_DUALSPEED=y
CONFIG_USB_GADGET_DOWNLOAD=y
CONFIG_USB_FUNCTION_MASS_STORAGE=y
CONFIG_USB_FUNCTION_ROCKUSB=y
CONFIG_USB_HOST_ETHER=y
CONFIG_USB_ETHER_ASIX=y
CONFIG_USB_ETHER_SMSC95XX=y
CONFIG_SYS_WHITE_ON_BLACK=y
CONFIG_FS_EXT4=y
CONFIG_FS_FAT=y
CONFIG_FAT_WRITE=y
CONFIG_FS_FAT_MAX_CLUSTSIZE=65536
CONFIG_HAVE_PRIVATE_LIBGCC=y
CONFIG_LIB_UUID=y
CONFIG_PRINTF=y
CONFIG_SPL_PRINTF=y
CONFIG_SPRINTF=y
CONFIG_SPL_SPRINTF=y
CONFIG_STRTO=y
CONFIG_SPL_STRTO=y
CONFIG_IMAGE_SPARSE=y
CONFIG_IMAGE_SPARSE_FILLBUF_SIZE=0x80000
CONFIG_USE_PRIVATE_LIBGCC=y
CONFIG_SYS_HZ=1000
CONFIG_USE_TINY_PRINTF=y
CONFIG_REGEX=y
CONFIG_LIB_RAND=y
CONFIG_CMD_DHRYSTONE=y
CONFIG_ERRNO_STR=y
CONFIG_OF_LIBFDT=y
CONFIG_SPL_OF_LIBFDT=y
CONFIG_GENERATE_SMBIOS_TABLE=y
CONFIG_SMBIOS_MANUFACTURER="rockchip"
CONFIG_EFI_LOADER=y
CONFIG_OPTEE_LOAD_ADDR=0x00000000

which I modified to default the ftd file to rk3288-tinkerS.dtb
Anyway I saw something interesting that definitely override the normal u-boot variables. I mean that some variable is oriented to a default which we don't expect to use, so assigning new ones will ensure to pick up the wanted ftd file, for example.

summers wrote:Anyway best of luck in crafting your own kernel

It's a little experiment, but I recon that you're right that is not a shareable condition. So I revert back to the standard.
TheSaint
 
Posts: 345
Joined: Mon Jul 23, 2018 7:57 am

Re: Asus TB S

Postby summers » Mon Aug 27, 2018 3:14 pm

That you got to a login almost certain says you managed to load the root fs. Alas console can be a bit noisy when you are getting error messages. Anyway at least with a login prompt, you can login and probe what the errors are.

Oh yes, that link you posted is probably a boot.txt - e.g. make in to a boot.scr and it should boot from it ...
summers
 
Posts: 868
Joined: Sat Sep 06, 2014 12:56 pm

Re: Asus TB S

Postby TheSaint » Tue Aug 28, 2018 6:07 am

Hey Summers, the best news ever :D
I booted and there are no debug messages, because of the SD card plugged in.
I check the WiFi and it is there !!!
Code: Select all
# ip link set dev wlan0 up
[  777.983793] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin
[  779.236640] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[root@alarm alarm]# ip link set dev wlan0 up
[root@alarm alarm]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 88:d7:f6:c2:f1:42 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:9f:38:dd:97:3b brd ff:ff:ff:ff:ff:ff

The block devices are all listed.
Code: Select all
# fdisk -l
Disk /dev/mmcblk0: 14.4 GiB, 15489564672 bytes, 30253056 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x58bc1052

Device         Boot   Start      End  Sectors  Size Id Type
/dev/mmcblk0p1         8192   139263   131072   64M  c W95 FAT32 (LBA)
/dev/mmcblk0p2       139264  8331263  8192000  3.9G 83 Linux
/dev/mmcblk0p3      8331264 30253055 21921792 10.5G 83 Linux


Disk /dev/mmcblk2: 14.7 GiB, 15758000128 bytes, 30777344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x89e2f1d4

Device         Boot Start     End Sectors Size Id Type
/dev/mmcblk2p1       8192 8396799 8388608   4G 83 Linux


Disk /dev/mmcblk2boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk2boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes


I give a longer try, but I fill we got it done :D
TheSaint
 
Posts: 345
Joined: Mon Jul 23, 2018 7:57 am

Re: Asus TB S

Postby summers » Tue Aug 28, 2018 8:58 am

Great!

just to check - which u-boot is this with?

Which device tree blob is this with?

If with both of mine, I'll start converting into patches - and sending into mainline. I'll do the kernel first, as its the device tree thats the important bit - and thats held in mainline ...
summers
 
Posts: 868
Joined: Sat Sep 06, 2014 12:56 pm

PreviousNext

Return to Community Supported

Who is online

Users browsing this forum: No registered users and 2 guests