Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
- I did get 4.3.3 compiled with CONFIG_REGULATOR_AXP20X, and as you said no help.
- I had a really hard time with initrd (glad zboot is enabled on banana at least I did not have to use uinitrd and uImage)
I ended up using the initrd-arm7 from /slackwarearm/slackwarearm-current/kernels/armv7
I got kernel zImage ok, pretty sure I made a DFD mistake (didn't follow directions)
Suspect I need to feed root=/dev/sda2 rootfs=ext4 to initrd
So I'll try again,
seems like arm does not support this ?
I ended up using the initrd-arm7 from /slackwarearm/slackwarearm-current/kernels/armv7
I got kernel zImage ok, pretty sure I made a DFD mistake (didn't follow directions)
Suspect I need to feed root=/dev/sda2 rootfs=ext4 to initrd
You don't need to do this - you specify the parameters in the u-boot configuration, as described in the 'INSTALL_' documents.
You could specify them in the initrd and omit them from u-boot, but the initrd supplied in Slackware ARM is generic and the settings it contains are relevant to the build machine on which the kernel was built, and isn't necessarily going to represent the user's environment -- hence why they are configured as kernel parameters through u-boot.
This isn't enabled because I don't see it's necessary for the stock kernels and it makes the kernels larger. If you want the config you can find it in /boot or on the FTP site.
So I think it's possible to get USB working with Linux 4.3 - it's just that some extra options need enabling.
I'm going to upgrade to Linux 4.3.5 and set the additional options -- I'm pretty sure it'll work.
Unfortunately there's a blocker on the Kirkwood platform with adopting 4.4, which I have raised a bug for: https://bugzilla.kernel.org/show_bug.cgi?id=111701
Unless that gets fixed before Slackware 14.2 is released, the kernel will be the latest 4.3 series.
There's a lot to getting working configs. (and a couple cycles compile time)
I'll likely stick with which ever kernel comes with 14.2, but if you still have it handy can you diff this against your config-armv7-4.4.0 https://www.dropbox.com/s/azwdno36ym...-4.4.0-v3?dl=0 I have not yet figured out which options to change in 4.4.0 to get some joy on the USBs with the banana.
Not critical since you always got irons in the fire
(I just made this by make oldconfig and trying to tweak)
There's a lot to getting working configs. (and a couple cycles compile time)
I'll likely stick with which ever kernel comes with 14.2, but if you still have it handy can you diff this against your config-armv7-4.4.0 https://www.dropbox.com/s/azwdno36ym...-4.4.0-v3?dl=0 I have not yet figured out which options to change in 4.4.0 to get some joy on the USBs with the banana.
Not critical since you always got irons in the fire
(I just made this by make oldconfig and trying to tweak)
If you look at the thread I posted, all I had to do was enable the additional regulator module.
The 4.4.0 config was make oldconfig'd from the 4.3 config, with nothing to do with USB or power (as I remember) added during the make oldconfig
However, in Linux 4.3 (trying to get USB working) I've added a number of modules which looked useful from a hardware PoV.
What I needed was:
CONFIG_PHY_SUN4I_USB
and its dependencies (in order to present that in the configuration tool).
The full diff between 4.3.4 and 4.3.5 is:
Code:
prisere [configs] # diff -u0 /tmp/config-armv7-4.3.4 config-armv7
--- /tmp/config-armv7-4.3.4 2016-02-03 13:48:43.500629282 +0000
+++ config-armv7 2016-02-03 11:26:55.291129527 +0000
@@ -3 +3 @@
-# Linux/arm 4.3.4 Kernel Configuration
+# Linux/arm 4.3.5 Kernel Configuration
@@ -3308,0 +3309 @@
+# CONFIG_AXP288_CHARGER is not set
@@ -4527 +4528 @@
-# CONFIG_USB_EHCI_MSM is not set
+CONFIG_USB_EHCI_MSM=m
@@ -4529 +4530 @@
-# CONFIG_USB_EHCI_EXYNOS is not set
+CONFIG_USB_EHCI_EXYNOS=m
@@ -4544 +4545 @@
-# CONFIG_USB_OHCI_EXYNOS is not set
+CONFIG_USB_OHCI_EXYNOS=m
@@ -4599,2 +4600,2 @@
-# CONFIG_USBIP_VHCI_HCD is not set
-# CONFIG_USBIP_HOST is not set
+CONFIG_USBIP_VHCI_HCD=m
+CONFIG_USBIP_HOST=m
@@ -4609,0 +4611 @@
+# CONFIG_USB_MUSB_SUNXI is not set
@@ -4629,0 +4632 @@
+CONFIG_USB_DWC3_OMAP=m
@@ -4635 +4638,11 @@
-# CONFIG_USB_DWC2 is not set
+CONFIG_USB_DWC2=m
+# CONFIG_USB_DWC2_HOST is not set
+
+#
+# Gadget/Dual-role mode requires USB Gadget support to be enabled
+#
+# CONFIG_USB_DWC2_PERIPHERAL is not set
+CONFIG_USB_DWC2_DUAL_ROLE=y
+CONFIG_USB_DWC2_PCI=m
+# CONFIG_USB_DWC2_DEBUG is not set
+# CONFIG_USB_DWC2_TRACK_MISSED_SOFS is not set
@@ -4727,2 +4740,2 @@
-# CONFIG_USB_HSIC_USB3503 is not set
-# CONFIG_USB_LINK_LAYER_TEST is not set
+CONFIG_USB_HSIC_USB3503=m
+CONFIG_USB_LINK_LAYER_TEST=m
@@ -4740 +4753 @@
-# CONFIG_AB8500_USB is not set
+CONFIG_AB8500_USB=m
@@ -4748 +4761,3 @@
-# CONFIG_USB_MXS_PHY is not set
+CONFIG_USB_MSM_OTG=m
+CONFIG_USB_QCOM_8X16_PHY=m
+CONFIG_USB_MXS_PHY=m
@@ -5399 +5414,11 @@
-# CONFIG_EXTCON is not set
+CONFIG_EXTCON=y
+
+#
+# Extcon Device Drivers
+#
+CONFIG_EXTCON_ADC_JACK=m
+CONFIG_EXTCON_AXP288=m
+CONFIG_EXTCON_GPIO=m
+CONFIG_EXTCON_RT8973A=m
+CONFIG_EXTCON_SM5502=m
+CONFIG_EXTCON_USB_GPIO=m
@@ -5672,2 +5697,2 @@
-# CONFIG_PHY_BERLIN_USB is not set
-# CONFIG_PHY_BERLIN_SATA is not set
+CONFIG_PHY_BERLIN_USB=m
+CONFIG_PHY_BERLIN_SATA=m
@@ -5676 +5701 @@
-CONFIG_PHY_EXYNOS_MIPI_VIDEO=y
+CONFIG_PHY_EXYNOS_MIPI_VIDEO=m
@@ -5687 +5712 @@
-CONFIG_PHY_EXYNOS_DP_VIDEO=y
+CONFIG_PHY_EXYNOS_DP_VIDEO=m
@@ -5690 +5715,2 @@
-# CONFIG_PHY_HIX5HD2_SATA is not set
+CONFIG_PHY_HIX5HD2_SATA=m
+CONFIG_PHY_SUN4I_USB=m
@@ -5691,0 +5718,5 @@
+CONFIG_PHY_SAMSUNG_USB2=m
+CONFIG_PHY_S5PV210_USB2=y
+CONFIG_PHY_EXYNOS4210_USB2=y
+CONFIG_PHY_EXYNOS4X12_USB2=y
+CONFIG_PHY_EXYNOS5250_USB2=y
@@ -5693,2 +5724,2 @@
-# CONFIG_PHY_QCOM_APQ8064_SATA is not set
-# CONFIG_PHY_QCOM_IPQ806X_SATA is not set
+CONFIG_PHY_QCOM_APQ8064_SATA=m
+CONFIG_PHY_QCOM_IPQ806X_SATA=m
@@ -5698 +5729 @@
-# CONFIG_PHY_QCOM_UFS is not set
+CONFIG_PHY_QCOM_UFS=m
@@ -6440,0 +6472 @@
+CONFIG_STMP_DEVICE=y
When going back to 4.4 I will make oldconfig from the 4.3 series configuration again and add in the regulator required for the A20.
Well got back from Holiday to find my BPi has power issues and will not power up. (I'll see if I can find any bad cap's on here not sure I can fix but...)
One thing I noticed looking closely at the board I found D5 is absolutely blown. (I did have a powered hub setup here at one time)
Which prompted me to look at what D5 was, found this..
Some users have been reporting hardware defects due to loss of VCC-5V, e.g. failure to power the USB (host) ports etc. Frequently this is related to a "D5 diode problem". The Banana Pi schematic lists this part (1N5819, SO-123) in the "VCC-5V" section, showing it feeds the VCC-5V line from the AXP209's IPSOUT. If you suspect a problem with D5, check the test points: if IPSOUT is okay and 5.0V absent, then D5 likely is the culprit. It might have blown, e.g. due to drawing too much current or using a "bad" USB hub that backpowered the Pi (when self-powered). Apparently there was even a batch of devices - first 1000 according to SinoVoip - where D5 was actually dimensioned too small.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.