andy-shev/linux

Linux kernel source tree

linux's Issues

SST probe error

Hi! When setting CONFIG_SND_MFLD_MACHINE=y the kernel tries to probe the SST PCI device intel_sst_probe, but fails in sst_context_init because platform data (pdata) is not set in the driver context. I guess, this needs to be done by a platform driver (sst-mfld-platform-pcm maybe?) or by a SFI driver (matching mrfld_sst) perhaps. I see that the platform data is being set in sst_acpi.c but as of now I am running a non-ACPI u-boot. Is this resolved with u-boot from the acpi branch? Or where's the appropriate spot to set the platform data? I see that you've done a few changes to the SST sources, Andy, did you get this to work?

IRQ #54 disabling on Edison 64-bit kernel

I have built a 64-bit 4.9 kernel from your 'eds' (8624493) branch and shortly after booting all the way to a command prompt I get an IRQ disabled stack trace.

dmesg.txt
edison64_config.txt
proc_interrupts.txt

Let me know what other details I should gather.

boot failure on SparkFun blocks (base or console)

I cloned https://github.com/andy-shev/linux and checked out the eds branch.
The tree is at e72aad722abd0a639a3ef4c42d8e59f4adc50d9e

On my desktop (Debian amd64, running stretch), I did:
$ make i386_defconfig
$ make ARCH=i386 -j4 bzImage
I copied bzImage to the /boot partition (/dev/mmcblk0p7) on my Edison.
I rebooted and entered U-Boot. I changed the bootargs as shown in the attached file and booted bzImage. Console output from the boot is attached, as is my kernel .config file.

Thanks for your time in looking at this.

uboot-settings.txt
console-output.txt
kernel-config.txt

Kernel won't boot

Hi guys,
I am using git://github.com/htot/linux.git , branch eds-4.11 which should be pretty much the same kernel as the one from this repo.
However, the kernel won't boot. It just hangs at "Starting kernel ..." forever.
Has anybody seen this with this kernel?
I am currently building this repository here also and giving it a try also
Thanks

eem gadget works only after cold reboot

This was with your configurations rebased on 5.10.24 (LTS) https://github.com/edison-fw/linux/commits/eds-acpi-5.10.24
I have bitbake apply 2 other (relevant) patches:

SRC_URI_append = " file://0001-HACK-do-not-enumerated-SFI-devices.patch"
SRC_URI_append = " file://0001-usb-dwc3-pci-Enable-dis_uX_susphy_quirk-for-Intel-Me.patch"

I'll highlight the interesting bits and have some conclusions at the end:

This is to test eem ethernet gadget (Connector USB 2 shown as 2 on the photo).

In these tests I leave edison-arduino switch in gadget mode (Switch 1 in the position as shown on the photo). Communication with edison is through console (Connector USB 1 shown as 3 on the photo)

1. Cold boot (press Edison reset button 7 sec), with USB 2 unplugged, wait for prompt, login, plug USB 2

root@yuna:~# connmanctl services
*AO Wired                gadget_aabbccddeef1_usb
...

root@yuna:~# ifconfig
...

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500  metric 1
        inet 10.42.0.221  netmask 255.255.255.0  broadcast 10.42.0.255
        inet6 fe80::a8bb:ccff:fedd:eef1  prefixlen 64  scopeid 0x20<link>
        ether aa:bb:cc:dd:ee:f1  txqueuelen 1000  (Ethernet)
        RX packets 45  bytes 7074 (6.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 43  bytes 6173 (6.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@yuna:~# iperf3 -s
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 10.42.0.1, port 50840
[  5] local 10.42.0.221 port 5201 connected to 10.42.0.1 port 50842
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  23.1 MBytes   193 Mbits/sec
[  5]   1.00-2.00   sec  24.1 MBytes   202 Mbits/sec
[  5]   2.00-3.00   sec  24.4 MBytes   205 Mbits/sec
[  5]   3.00-4.00   sec  24.4 MBytes   205 Mbits/sec

On host (run 2 min, at 200Mb/sec Edison doesn't crash in other cases often does)

ferry@delfion:~$ iperf3 -c 10.42.0.221 -t 0
Connecting to host 10.42.0.221, port 5201
[  5] local 10.42.0.1 port 50842 connected to 10.42.0.221 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  26.7 MBytes   224 Mbits/sec    0   1.12 MBytes
[  5]   1.00-2.00   sec  23.8 MBytes   199 Mbits/sec   49   1.13 MBytes
[  5]   2.00-3.00   sec  23.8 MBytes   199 Mbits/sec    0   1.25 MBytes
[  5]   3.00-4.00   sec  25.0 MBytes   210 Mbits/sec    0   1.34 MBytes
[  5]   4.00-5.00   sec  23.8 MBytes   199 Mbits/sec    0   1.40 MBytes
[  5]   5.00-6.00   sec  25.0 MBytes   210 Mbits/sec   14   1.04 MBytes
...
[  5] 157.00-158.00 sec  0.00 Bytes  0.00 bits/sec    0   1.21 MBytes
[  5] 158.00-159.00 sec  0.00 Bytes  0.00 bits/sec    0   1.21 MBytes
^C[  5] 159.00-159.32 sec  0.00 Bytes  0.00 bits/sec    0   1.21 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-159.32 sec  3.41 GBytes   184 Mbits/sec  294             sender
[  5]   0.00-159.32 sec  0.00 Bytes  0.00 bits/sec                  receiver
iperf3: interrupt - the client has terminated

2. kill iperf3 on Edison, unplug USB 2, wait 5 sec, plug USB 2

root@yuna:~# connmanctl services
*AO Wired                gadget_aabbccddeef1_usb

(A = autoconnected, O connection pinged intel.com)

root@yuna:~# iperf3 -s
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 10.42.0.1, port 50914
[  5] local 10.42.0.221 port 5201 connected to 10.42.0.1 port 50916
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  4.62 MBytes  38.8 Mbits/sec
[  5]   1.00-2.00   sec  1017 KBytes  8.33 Mbits/sec
[  5]   2.00-3.00   sec   672 KBytes  5.50 Mbits/sec
[  5]   3.00-4.00   sec   342 KBytes  2.80 Mbits/sec
[  5]   4.00-5.00   sec   365 KBytes  2.99 Mbits/sec
[  5]   5.00-6.00   sec   380 KBytes  3.12 Mbits/sec
[  5]   6.00-7.00   sec   329 KBytes  2.70 Mbits/sec
[  5]   7.00-8.00   sec  90.5 KBytes   742 Kbits/sec
[  5]   8.00-9.00   sec  3.14 MBytes  26.3 Mbits/sec
[  5]   9.00-10.00  sec   126 KBytes  1.03 Mbits/sec
[  5]  10.00-11.00  sec   776 KBytes  6.36 Mbits/sec

On host

ferry@delfion:~$ iperf3 -c 10.42.0.221 -t 0
Connecting to host 10.42.0.221, port 5201
[  5] local 10.42.0.1 port 50916 connected to 10.42.0.221 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  6.18 MBytes  51.8 Mbits/sec    2    260 KBytes
[  5]   1.00-2.00   sec   827 KBytes  6.77 Mbits/sec    1    296 KBytes
[  5]   2.00-3.00   sec   827 KBytes  6.77 Mbits/sec    0    327 KBytes
[  5]   3.00-4.00   sec  0.00 Bytes  0.00 bits/sec    1    342 KBytes
[  5]   4.00-5.00   sec   891 KBytes  7.30 Mbits/sec    0    359 KBytes
[  5]   5.00-6.00   sec  0.00 Bytes  0.00 bits/sec    0    378 KBytes
[  5]   6.00-7.00   sec   891 KBytes  7.30 Mbits/sec    0    393 KBytes
[  5]   7.00-8.00   sec  0.00 Bytes  0.00 bits/sec    0    397 KBytes
[  5]   8.00-9.00   sec  4.41 MBytes  37.0 Mbits/sec    1    566 KBytes
[  5]   9.00-10.00  sec  0.00 Bytes  0.00 bits/sec    1    568 KBytes
...
[  5] 120.00-121.00 sec  0.00 Bytes  0.00 bits/sec    0   3.74 MBytes
[  5] 121.00-122.00 sec  0.00 Bytes  0.00 bits/sec    0   3.74 MBytes
[  5] 122.00-123.00 sec  0.00 Bytes  0.00 bits/sec    0   3.75 MBytes
[  5] 123.00-124.00 sec  0.00 Bytes  0.00 bits/sec    0   3.75 MBytes
[  5] 124.00-125.00 sec  1.25 MBytes  10.5 Mbits/sec    0   3.75 MBytes
^C[  5] 125.00-125.41 sec  0.00 Bytes  0.00 bits/sec    0   3.75 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-125.41 sec  53.9 MBytes  3.61 Mbits/sec  431             sender
[  5]   0.00-125.41 sec  0.00 Bytes  0.00 bits/sec                  receiver
iperf3: interrupt - the client has terminated

3. warm reboot Edison with USB 2 plugged: no change
4. warm reboot Edison with USB 2 unplugged: plug event seems not detected, other gadgets do not appear (sound, mass storage)
   But connman thinks gadget is there, powered, but not connected:

root@yuna:~# connmanctl technologies
...
/net/connman/technology/gadget
  Name = Gadget
  Type = gadget
  Powered = True
  Connected = False
  Tethering = False

And device is standbye (R) but not pinging intel.com.

root@yuna:~# connmanctl services
*AR Wired                gadget_aabbccddeef1_usb

Didn't receive correct config from dhcp (or not at all)

root@yuna:~# ifconfig
...

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500  metric 1
        inet 169.254.147.69  netmask 255.255.0.0  broadcast 169.254.255.255
        inet6 fe80::a8bb:ccff:fedd:eef1  prefixlen 64  scopeid 0x20<link>
        ether aa:bb:cc:dd:ee:f1  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

5. Cold reboot with USB 2 plugged: same as with cable unplugged.

6. Warm reboot with USB 2 plugged (network in good state): device is standbye (R) but not pinging intel.com.

7. Cold reboot, then Warm reboot with USB 2 unplugged, connected but bad:

ferry@delfion:~$ iperf3 -c 10.42.0.221 -t 0
Connecting to host 10.42.0.221, port 5201
[  5] local 10.42.0.1 port 51216 connected to 10.42.0.221 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  6.97 MBytes  58.4 Mbits/sec    2    303 KBytes
[  5]   1.00-2.00   sec  1.43 MBytes  12.0 Mbits/sec    1    361 KBytes
[  5]   2.00-3.00   sec  1.93 MBytes  16.2 Mbits/sec    0    419 KBytes
[  5]   3.00-4.00   sec  4.67 MBytes  39.2 Mbits/sec    0    605 KBytes
[  5]   4.00-5.00   sec  2.50 MBytes  21.0 Mbits/sec    1    707 KBytes
[  5]   5.00-6.00   sec  0.00 Bytes  0.00 bits/sec    0    731 KBytes

8. Cold reboot with USB 2 plugged:

root@yuna:~# connmanctl disable gadget

unplug USB 2, wait 5 sec, plug USB 2:

root@yuna:~# connmanctl enable gadget
ferry@delfion:~$ iperf3 -c 10.42.0.221 -t 0
Connecting to host 10.42.0.221, port 5201
[  5] local 10.42.0.1 port 40422 connected to 10.42.0.221 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  25.6 MBytes   215 Mbits/sec    0   1.10 MBytes       
[  5]   1.00-2.00   sec  25.0 MBytes   210 Mbits/sec   89   1.16 MBytes       
[  5]   2.00-3.00   sec  23.8 MBytes   199 Mbits/sec    0   1.28 MBytes       
[  5]   3.00-4.00   sec  23.8 MBytes   199 Mbits/sec    0   1.38 MBytes       
[  5]   4.00-5.00   sec  25.0 MBytes   210 Mbits/sec   11   1.02 MBytes       
[  5]   5.00-6.00   sec  25.0 MBytes   210 Mbits/sec    0   1.09 MBytes       
[  5]   6.00-7.00   sec  23.8 MBytes   199 Mbits/sec    0   1.14 MBytes       
^C[  5]   7.00-7.39   sec  10.0 MBytes   214 Mbits/sec    0   1.16 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-7.39   sec   182 MBytes   206 Mbits/sec  100             sender
[  5]   0.00-7.39   sec  0.00 Bytes  0.00 bits/sec                  receiver
iperf3: interrupt - the client has terminated

Conclusion

• On cold boot dwc3 eem gadget works fine.
• Unplug/replug messes up the driver or the hardware, warm reboot does not reset this behavior.
• In working state, disabling the eem gadget with connmanctl (I believe this to be the same as ip link set dev usb0 down), plug/replug followed by enabling again, eem gadget works.

ttyS1 on edison_arduino won't work (linux 4.11)

I have tried this with screen /dev/ttyS1 115200 (running on edison) and with a small program that writes 65 bytes out and reads back whatever is in the buffer (currently read exactly 0 bytes). I have RX and TX looped back of course.

External driver direction set with:

# 0 - RX  
# rx (input) is on pin 130, level translator direction must be set on 248
echo 248 > /sys/class/gpio/export 
echo low > /sys/class/gpio/gpio248/direction  # set to input
echo 216 > /sys/class/gpio/export 
echo in > /sys/class/gpio/gpio216/direction  # no pullup

# 1 - TX  
# tx (output) is on 131, level translator direction must be set on 249
echo 249 > /sys/class/gpio/export
echo high > /sys/class/gpio/gpio249/direction  # set to output
echo 217 > /sys/class/gpio/export  
echo in > /sys/class/gpio/gpio217/direction # no pullup

I can not set direction on 130/131 as that claims them for gpio, so I assume hsu driver take care of pinctrl and pinmux (once claimed I don't know how to release back to hsu, except by reboot).

Of course ttyS2 is used for the console and works fine. According to:

cat /sys/kernel/debug/pinctrl/pinctrl-merrifield/pins
pin 121 (GP130_UART_1_RX) mode 1 0x00003001
pin 122 (GP131_UART_1_TX) mode 1 0x00003001
pin 125 (GP134_UART_2_RX) mode 1 0x00003121
pin 126 (GP135_UART_2_TX) mode 1 0x00003121

all should be in mode 1, however there is a difference in the other bits.

What am I doing wrong here?

[Feature Request] Edison: Battery level reporting

I see you are working on the power button lately. If I may suggest a likely-related (on which-chip-does-what level) feature I would like to see working on the edison, it is getting battery level and power source information. I believe these come from the TI-developed, Intel-specific, specs-unavailable PMIC.

eds branch fails to boot when rebased to Linux 5.4-rc1

I have been using the eds branch with my Intel Edison boards, manually rebasing your patches to newer Linux kernels. I have been successful in getting functioning kernel images for Linux 5.1, 5.2, and 5.3, but I am unable to get a working kernel image by rebasing your patches to Linux 5.4-rc1.

For starters, fa01aff conflicts with 7bd4227, cause a build failure. I tried to resolve the problem by reverting fa01aff, which allowed the build to succeed, but the kernel booted with no messages on the serial console, and after some time the watchdog kicked in automatically to reboot the device.

I understand that your attention may now be elsewhere, given that Edison had been discontinued over two years ago. Still, it would be nice to have the board working on Linux 5.4, which is going to be an LTS release.

Thank you!

Reboot problem on Edison with 3.3V supply

Hi,

We have a custom board that supplies the Edison module with 3.3V(VSYS voltage).
We are using the 4.13.0 kernel, compiled from this git repo.
When we give the reboot command, the system hangs.

The only log is the one bellow, without PSH kernel and u-boot starting anymore:

root@d29029e:~# reboot
[ 6213.027804] reboot: Restarting system

If we put the Edison module in the mini breakout board, reboot works fine. The mini breakout board supplies the Edison module with 4.4V.

Also, if we flash our Edison module with 3.10.98 kernel for edison, reboot works even on the custom hardware.

Since the old kernel had source code for Merrifield PMU, I'm thinking that lacking the PMU code in the 4.13.0 kernel could causes the reboot problem.

Do you think this could be the case?

Thanks!

eds branch kernel works in 32-bit mode, but not in 64-bit mode

Is the kernel from eds branch supposed to work on Edison in 64-bit mode?

If I build the kernel (current eds branch head, 01e5c69a4f4a13d43e753157a5602b1d8c690469) in i386 architecture, the kernel boots fine on Intel Edison with mini-breakout board. But if I build with x86_64 architecture using the same kernel source, the kernel fails to boot on the same Edison board. This is what I see on the serial console:

reading vmlinuz2
6727072 bytes read in 164 ms (39.1 MiB/s)
Valid Boot Flag
Setup Size = 0x00003e00
Magic signature found
Using boot protocol version 2.0d
Linux kernel version 4.8.0-rc6-barb+ (user@common) #1 SMP Tue Sep 13 21:29:38 PDT 2016
Building boot_params at 0x00090000
Loading bzImage at address 00100000 (6711200 bytes)
Magic signature found
Kernel command line: "rootwait root=PARTUUID=012b3303-34ac-284d-99b4-34e03a2335f4 rootfstype=ext4 console=tty1 console=ttyS2,115200n8 console=ttyMFD2 loglevel=8 g_multi.ethernet_config=cdc systemd.unit=multi-user.target hardware_id=00 g_multi.iSerialNumber=28b8e149bda6b46f643f266147d3be59 g_multi.dev_addr=02:00:86:d3:be:59 platform_mrfld_audio.audio_codec=dummy"

Starting kernel ...

And then nothing happens, until the watchdog kicks in and reboots the system.

I built the kernels using the standard "make -j4" command, with gcc (Debian 6.1.1-11) 6.1.1 20160802 on a x86_64 Linux system running Debian testing. The kernel configs are generated from i386_defconfig and x86_64_defconfig, respectively, and everything else (even the kernel boot arguments provided by u-boot) are the same.

The page https://edison.internet-share.com/wiki/Using_a_vanilla_Linux_kernel_with_Intel_Edison states that Linux 4.4 boots on Edison in 64-bit mode, so I was hoping that the latest eds branch would also work in 64-bit mode. But perhaps there has been a regression?

Any help would be appreciated. Please let me know if I can provide more information to help with troubleshooting. Thanks!

config-x86_64.txt

How to use yocto build for intel eds branch?

Hi,

How can i use eds branch in the yocto environment of intel edison.
The current recipee is using 3.10 kernel. I just replaced the git repository and the branch to use eds branch and it fails to build.
Is there a standard way how I should use this branch on yocto environment? If not, I will try to put my debug information here.

Thank you!

thinkpad battery: force-discharge and inhibit-charge

These patches introduce support for

• force the battery to discharge when AC is attached
• hold battery charging via a manual override called Inhibit Charge

on Lenovo ThinkPads.

[1] https://gist.github.com/linrunner/31ab2f83c986e640ce8f7a4032d81a28
[2] https://gist.github.com/linrunner/5109b0ed2655fdcaf88a30a0303125bf
[3] https://gist.github.com/linrunner/fd07193578e07f16a5c1c9af3309f0d2

They have been tested and work.
Would it be possible to merge them?
Thanks.

eds branch changed?

Hi,
we are using this kernel and been using this revision: 54f9552
However, today I see this revision is not in the git tree anymore. Was there a git rewrite on your side?

Thank you

I2C-6 Doesn't Work

As was previously mentioned on the Intel forums, i2c-6 doesn't work with the newer kernels because it requires setting the pin mux. Intel had previously exported this functionality through a (somewhat clunky) debugfs interface that worked with the old version of the GPIO driver included with the official 3.x kernels.

For a project I'm working on, I need both I2C buses. What would it take to get i2c-6 working, both temporarily and in a way that could be sent upstream? I'm willing to work on this and to learn, but have limited background with Linux kernel development (took an operating systems course using a teaching kernel, but never contributed to Linux).

So far, I've considered writing a userspace program that sets the pin mux, but it looks like the I2C pins are in a protected region that requires using an IPC channel. This rules out a userspace program because that would be complicated and we couldn't safely lock the IPC.

It looks like much of the groundwork has been done for this in pinctrl-merrifield.c. What is the appropriate place to be calling the pinctrl code from?

Wifi not detected

My understanding is that wifi should be working on the Edison, but I'm unable to see the device (I'm using an Intel mini-breakout board). I've tried with the i368_defconfig and others but I must be missing something.

Can someone post a known-working .config file that boots on a mini-breakout and has working wifi?

Wi-fi support

Hi, I'm trying to get wi-fi to work, but I'm having no luck so far. I learned that mainline 4.8 kernel doesn't have the patches to enable the mmc host and regulator for the wi-fi chip, but even the current tip (2cbbee3) of your eds branch doesn't seem to work.

Excerpts from dmesg:

[    0.129318] bcm43xx-vmmc-regulator: Failed to request enable GPIO96: -517
[    0.129541] reg-fixed-voltage reg-fixed-voltage.0.auto: Failed to register regulator: -517
…
[    0.705322] sdhci: Secure Digital Host Controller Interface driver
[    0.705327] sdhci: Copyright(c) Pierre Ossman
[    0.705394] sdhci-pci 0000:00:01.0: SDHCI controller found [8086:1190] (rev 1)
[    0.714112] mmc0: SDHCI controller on PCI [0000:00:01.0] using ADMA
[    0.714203] sdhci-pci 0000:00:01.2: SDHCI controller found [8086:1190] (rev 1)
[    0.723140] mmc1: SDHCI controller on PCI [0000:00:01.2] using ADMA
[    0.723417] sdhci-pci 0000:00:01.3: SDHCI controller found [8086:1190] (rev 1)
[    0.732260] mmc2: SDHCI controller on PCI [0000:00:01.3] using ADMA
[    0.732511] sdhci-pltfm: SDHCI platform and OF driver helper
…
[    0.752916] bcm43xx-vmmc-regulator: at 2000 mV 
[    0.756369] reg-fixed-voltage reg-fixed-voltage.0.auto: bcm43xx-vmmc-regulator supplying 2000000uV
…
[    0.756812] bcm43xx-vmmc-regulator: disabling

Modprobing brcmfmac does not result in any output to dmesg.

The first line looks a bit suspect, but I assume it's because the GPIO driver is not initialized yet at the time. It seems like the regulator driver gets reinitialized at some point because /sys/kernel/debug/gpio later indicates it's controlling the GPIO.

gpiochip0: GPIOs 0-191, parent: pci/0000:00:0c.0, 0000:00:0c.0:
 gpio-77  (                    |sd_cd               ) in  hi IRQ
 gpio-96  (                    |bcm43xx-vmmc-regulat) out lo    

I tried removing the regulator driver and controlling GPIO 96 manually, but that didn't help.

4.11 does not load rootfs from mmc

I have the u-boot edison-v2017.05 and built the 32bits 4.11 version of the kernel, loaded that to the FAT formated part 9 and used:

fw_setenv bootcmd_edsboot 'setenv bootargs ${bootargs_edsboot}; run load_edsboot; run boot_edsboot'
fw_setenv bootargs_edsboot 'console=tty1 console=ttyS2,115200n8 rootwait root=PARTUUID=012b3303-34ac-284d-99b4-34e03a2335f4 rootfstype=ext4'
fw_setenv load_edsboot 'load mmc 0:9 0x100000 bzImage'
fw_setenv boot_edsboot 'zboot 0x100000'

The kernel boots fine up to the point:
[ 2.432544] md: Waiting for all devices to be available before autodetect
[ 2.439398] md: If you don't use raid, use raid=noautodetect
[ 2.446107] md: Autodetecting RAID arrays.
[ 2.450279] md: autorun ...
[ 2.453122] md: ... autorun DONE.
[ 2.456551] Waiting for root device PARTUUID=012b3303-34ac-284d-99b4-34e03a2335f4...

And sits there (no watchdog reset). The partition is the original rootfs that is booted by the yocto kernel, on the mmc.

USB host on Edison

Hi -

I can get HEAD of https://github.com/andy-shev/linux/tree/eds to boot fine, but USB doesn't seem to work correctly as host (even with an OTG cable and several devices that work using the Intel supplied 3.10 kernel).

Is this a known limitation? If not, what driver is used for the USB on the Edison. xhci loads automatically for this kernel.

unloading SDIO kernel module

Recently i stumble upon the issue where some Edison GPIOs where could not write on them because they were reserved for the SD:
https://communities.intel.com/thread/77677

I know i can compile a kernel without that module. But i would prefer to be able to unload /load it at runtime.
I don't enought about kernels to actually know where to look to see if this kernel allows this.
Can you guide me?

Thanks

Support for Galileo gen 1?

Hey there.

I got this repo link from Stack Overflow, I see you're working on a kernel that works on Quark.

I have 2 x Gen 1 Galileos I want to try to do something interesting with before they go in the garbage (Like running a proper linux distro).

I noticed in a commit message that Gen 2 minimum is required. Does that mean Gen 1 definitely wont work and a lost cause?

Assistance with installation

Hi there!

Thank you SO much for your tireless efforts to build this repo, it is a fantastic resource. I am attempting to install Linux onto an Intel Galileo Gen 2, but with my inexperience installing Linux I'm getting rather confused.

I have been trying to follow this StackOverflow issue but am getting confused between these instructions, these instructions and also this repo which has these instructions.

Which should I use please? I thought simply using these instructions would be enough, but following them doesn't seem to work as the Galileo doesn't boot into Linux and am also getting confused as in the intel/common instructions, it mentions I need to build my own kernel, which is not mentioned.

Thank you SO much!!

Intel Edison does not work on Linux 4.7+ kernels

Hi Andy,

I have attached the kernel config and dmesg log for a mainline 4.6.7 kernel that boots and has serial console output on Intel Edison.

I have attempted to use the attached config as a base for 4.7.0 and newer kernels, but can't seem to get the 8250 serial console to work.

Let me know if there is anything else I can do to help and thanks for taking a look at this!

-Anderson
dmesg.txt
edison_config.txt

Bluetooth broken on 4.14

Looks like bt support broke in 4.14. I now get:

root@edison:~# /usr/bin/btattach  -B /dev/ttyS0 -P bcm -S 3000000
Attaching Primary controller to /dev/ttyS0
Switched line discipline from 0 to 15
Failed to set protocol: Protocol not supported
No controller attached

If I remember correctly for sure in 4.12, maybe also 4.13.

SoC_DT0 and SoC_DT1 (Intel temperature sensors) are not available

Hi,

The intel temperature drivers are not available in yocto thud (edison-fw/meta-intel-edison) version.
I have tried to enable the drivers in the kernel with no success.
Can you point out what are the kernel configuration parameters I need to enable/disable so that I can access the intel temperature sensors trough /sys/class/thermal/ interface?

Thank you,
Razvan

Problem accessing GPIO pin 23 (SPI) on an Explorer board

Hi @andy-shev

I am trying to get a TI CCxxxx chip working on an Intel Edison Explorerboard (see https://github.com/EnhancedRadioDevices/915MHzEdisonExplorer ) with your eds branch 4.10rc4.

I now have the /dev/spidev5.1 file and I also have a /sys/class/gpio/export file

# ls -al /sys/class/gpio/export
--w------- 1 root root 4096 Jan  1  2000 /sys/class/gpio/export

Unfortunately accessing the GPIO pin 23 fails, e.g.:

# reset_spi_serial.py
Traceback (most recent call last):
  File "/usr/local/bin/reset_spi_serial.py", line 6, in <module>
    exec(compile(open(__file__).read(), __file__, 'exec'))
  File "/root/src/915MHzEdisonExplorer_SW/spi_serial/scripts/reset_spi_serial.py", line 3, in <module>
    s = spi_serial.SpiSerial()
  File "/root/src/915MHzEdisonExplorer_SW/spi_serial/spi_serial/spi_serial.py", line 7, in __init__
    self.cs0 = m.Gpio(23)
  File "/usr/local/lib/python2.7/dist-packages/mraa.py", line 995, in __init__
    this = _mraa.new_Gpio(pin, owner, raw)
ValueError: Invalid GPIO pin specified

This works fine on a Yocto image. Can you explain why I can't access the spi serial pin?

My libmraa version v1.5.1-18-ge386300

This is also discussed on the Intend-to-Bolus gitter, see: https://gitter.im/nightscout/intend-to-bolus?at=588532efd43728124e8ef673 . @ecc1 and @oskarpearson helped me add some of the necessary kernel parameters. I enabled CONFIG_I2C_GPIO, CONFIG_SPI_GPIO, CONFIG_GPIO_SYSFS on your x86_64_defconfig

Thanks in advance,

Pieter

Feature request: branch of eds after each linux release

Hello Andy,

I am working to update meta-intel-edison to poky morty and to incorporate your u-boot and linux repositories. That will hopefully encourage more people to upgrade to your kernel. The good news that it already builds kernel, u-boot and root-fs images! Now I need to prepare to flash and check that it actually boots, so I can upload that work to github.
It would be nice if the resulting images would be based on more or less stable kernels, however your eds HEAD tracks kernel rc's with your patches applied. Would it be possible to create a branch with the latest released kernel (with your patched applied)?
Currently I am cloning a07f946, but that will break of course when you rebase to the next kernel rc.

Ferry