Hi Siarhei, On 03/14/2017 08:26 PM, Siarhei Siamashka wrote: > On Tue, 14 Mar 2017 18:01:11 +0900 > Jaehoon Chung <jh80.ch...@samsung.com> wrote: > >> On 03/14/2017 04:52 PM, Siarhei Siamashka wrote: >>> On Mon, 6 Mar 2017 12:18:50 +0200 >>> Siarhei Siamashka <siarhei.siamas...@gmail.com> wrote: >>> >>>> On Thu, 12 Jan 2017 14:02:48 +0530 >>>> Anand Moon <linux.am...@gmail.com> wrote: >>>> >>>>> Hi All, >>>>> >>>>> I tried to compile the latest u-boot for Odroid U3. >>>>> issue is that Ethernet is not able to detected. >>>>> >>>>> Please let me know what need to enable USB Ethernet >>>>> to support tftp boot. >>>>> >>>>> Best Regards >>>>> -Anand >>>>> >>>>> ------ >>>>> U-Boot 2017.01-02075-g4386feb-dirty (Jan 12 2017 - 06:17:08 +0000) >>>>> >>>>> CPU: Exynos4412 @ 1 GHz >>>>> Model: Odroid based on Exynos4412 >>>>> Board: Odroid based on Exynos4412 >>>>> Type: u3 >>>>> DRAM: 2 GiB >>>>> LDO20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling >>>>> LDO22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling >>>>> LDO21@TFLASH_2.8V: set 2800000 uV; enabling >>>>> MMC: SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1 >>>>> *** Warning - bad CRC, using default environment >>>>> >>>>> Net: No ethernet found. >>>>> Hit any key to stop autoboot: 0 >>>>> Odroid # >>>>> Odroid # >>>>> Odroid # usb start >>>>> starting USB... >>>>> USB0: USB EHCI 1.00 >>>>> scanning bus 0 for devices... 1 USB Device(s) found >>>>> scanning usb for ethernet devices... 0 Ethernet Device(s) found >>>>> Odroid # >>>>> Odroid # >>>>> Odroid # setenv usbethaddr 02:DE:AD:BE:EF:FF >>>>> Odroid # usb start >>>>> Odroid # usb info >>>>> 1: Hub, USB Revision 2.0 >>>>> - u-boot EHCI Host Controller >>>>> - Class: Hub >>>>> - PacketSize: 64 Configurations: 1 >>>>> - Vendor: 0x0000 Product 0x0000 Version 1.0 >>>>> Configuration: 1 >>>>> - Interfaces: 1 Self Powered 0mA >>>>> Interface: 0 >>>>> - Alternate Setting 0, Endpoints: 1 >>>>> - Class Hub >>>>> - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms >>>>> >>>>> Odroid # reset >>>> >>>> Hi Anand, >>>> >>>> It's an old problem and we have identified its root cause a long >>>> time ago: >>>> >>>> https://lists.denx.de/pipermail/u-boot/2015-October/231061.html >>>> >>>> Basically, a voltage regulator is not getting initialized because >>>> a call to the board_usb_init() function was lost during the DM >>>> conversion. You can try to compile U-Boot from my branch, it contains >>>> the rebased fixes which I have been using all this time on my ODROID-X >>>> board: >>>> >>>> https://github.com/ssvb/u-boot/commits/20170306-unbreak-odroid >>>> >>>> I did all the initial investigation back in 2015, but tried to >>>> delegate the actual bugfixing work to the ODROID board maintainer(s). >>>> Apparently it did not fly and ODROID support is still broken. >>>> >>>> If you can test my branch and confirm that it works on your ODROID-U3, >>>> then I can maybe spend some time on making cleaner patches and ensuring >>>> that they reach the U-Boot git repository. >>>> >>>> Thanks! >>> >>> Hello again, >>> >>> Anand Moon, considering no reply to my post, do I understand it >>> right that you are actually not very much interested in getting >>> this particular problem resolved in U-Boot? >>> >>> These ODROID problems are relatively simple and don't require any >>> special skills or considerable efforts to resolve. The only issue >>> is that apparently almost nobody uses the mainline U-Boot on this >>> hardware and nobody gives rats about having it usable out of the >>> box. >>> >>> I only have an ODROID-X board, which is a rather early and >>> short-lived revision. Again, if you or anybody else could step in >>> and take care of testing the fixes on other ODROID boards (X2 and >>> U3), then we could get ODROID boards working properly in the next >>> U-Boot release. >>> >>> >>> Jaehoon Chung, you seem to be listed as the current nominal ODROID >>> boards maintainer. But you don't seem to be doing anything other >>> than just making promises to check various things and then >>> disappearing for months/years: >> >> Actually, i had forgotten this mail...When i check the patches, first >> i'm looking at patchwork. And I'm remembering what i do and need. >> Right, it's my mistake for forgetting it. >> >> Disappearing for months/years? > > Yes, exactly. And that's what has already happened twice. > > "Once is happenstance, twice is coincidence, the third time it's > enemy action" ;-) But don't take it too seriously. I have > no intention to blame anybody because this is not moving us > anywhere. > >> If i decided to do nothing, i might not reply anything to u-boot >> mailing list. > > BTW, thanks for replying.
Sorry for late..It was my holidays. > >> If you send the polite reminding ping mail, maybe i will really >> apologize to you. but now i don't have those mind. >> You're regarding to me like nothing to do... >>> >>> https://lists.denx.de/pipermail/u-boot/2017-January/277954.html >>> https://lists.denx.de/pipermail/u-boot/2015-October/231023.html >> >> I can't access this URL,,so i don't know what you added.. > > This URL is the official U-Boot mailing list archive. Can you > explain what's going on and why you can't access it? The mailing > list admin might be interested in resolving issues (if there > are any). It's affected to our company firewall problem. Sometime, i can't access the some URL because of it. I think you can understand this situation. > >>> >>> Could you please explain what's going on and what are your plans >>> regarding ODROID boards support in U-Boot? >> >> I'm preparing to covert to DM from legacy..For converting DM, >> I'm doing step by step for samsung SoCs. >> Goni -> Universal210 - > Trats -> Trats2 -> Odroid also.. >> You can see my patches for goni, universal210, trats.. > > Well, looks like you have a lot on your plate. It's not > surprising that you have no time for maintaining Exynos > based ODROID boards. > > Still it's only my opinion, but it looks like you got your > priorities wrong. The DM conversion is more like a refactoring > and code massaging activity. It offers exactly nothing to the > end users. First, Samsung SoCs maintainer had requested to convert to DM. If Samsung didn't convert to DM, U-boot maintainers mentioned "Will remove the board files". > > Yes, the idea is that these refactoring changes can make the > code cleaner, more reusable and easier to maintain, which may > result in better quality and reliability in the long run. > Yada yada bla bla bla. > > However we have a bitrotten crap in the mainline U-Boot right > now (both MMC and USB are buggered on Exynos based ODROID boards) > and it has been this way since at least 2015. Yes, people are > already used to this and accept it as a norm, so they don't > complain much. I don't know what they are using right now on > their hardware. Maybe the Hardkernel's bootloader? Or an old > U-Boot release? Yes, If i didn't check about odroid series. So maybe you're right. Your opinion was motivated to think what i'm doing and what i have a plan. Thanks for it. > > IMHO making sure that the *current* U-Boot release works > correctly should be the first priority of the ODROID boards > maintainer. Rather than entertaining himself with a fun DM > stuff... but I mentioned above why i did for DM..So i think you can understand it. It's not for only enjoying. > >> I'm not sure this problem is fixed or not.. > > You could just boot your ODROID-U3 board and easily check whether > the Ethernet bug is still there or not. That's what you have > actually promised back in January. Actually, i missed this case...and i did some important tasks for company. It seems that sounds excuse.. > >> if you want to fix it, i will do it..but not right now. >> I keep going my current task.. > > OK, I'll take care of it. But as I said, I would need > ODROID-X2 and ODROID-U3 owners to test the fixes because > I don't have a full set of hardware. If you can send the patches..i can test all odroid boards. Finally, i have a time for it. Best Regards, Jaehoon Chung > _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
