#linux-rockchip on 2014-12-05 — irc logs at freenode.irclog.whitequark.org

2014-10-07 12:46 ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at http://linux-rockchip.info | Logs at http://irclog.whitequark.org/linux-rockchip | ML at http://groups.google.com/group/linux-rockchip

00:02 naobsd has joined #linux-rockchip

00:06 RayFlower has quit [Read error: Connection reset by peer]

00:07 RayFlower has joined #linux-rockchip

00:09 RayFlower has quit [Read error: Connection reset by peer]

00:09 RayFlower has joined #linux-rockchip

00:25 naobsd has quit [Quit: Page closed]

00:52 naobsd has joined #linux-rockchip

01:01 naobsd_ has joined #linux-rockchip

01:01 naobsd has quit [Ping timeout: 246 seconds]

01:05 RayFlower has quit [Read error: Connection reset by peer]

01:05 RayFlower has joined #linux-rockchip

01:18 levd has joined #linux-rockchip

01:25 field^Mop has quit [Ping timeout: 244 seconds]

01:35 levd1 has joined #linux-rockchip

01:37 levd has quit [Ping timeout: 272 seconds]

01:57 levd has joined #linux-rockchip

02:00 levd1 has quit [Ping timeout: 260 seconds]

02:04 cnxsoft has joined #linux-rockchip

02:12 levd1 has joined #linux-rockchip

02:13 Tony__ has joined #linux-rockchip

02:13 <Tony__> naobsd_, hi. may I ask a question about CodeStyle ?

02:14 <Tony__> AFAIK, there is script to check codeStyle in kernel tree.

02:14 <amstan> Tony__: it's usually a good idea to just ask questions on irc, don't ask to ask

02:14 levd has quit [Ping timeout: 250 seconds]

02:14 <Tony__> amstan, okay, :P

02:15 <Tony__> And My question is that is there a script to check codStyle in AOSP ?

02:15 <Tony__> *codeStyle

02:16 <amstan> Tony__: aosp as in android?

02:16 <amstan> it might depend on what code you're talking about, but http://developer.android.com/tools/help/lint.html might help

02:17 <Tony__> Yep, Android source tree.

02:17 <Tony__> Cpp/Java/C etc.

02:18 <amstan> Tony__: if you're talking about android kernel, it's probably just the linux kernel style

02:20 <Tony__> amstan, I know how to check the codestyle of kernel whateven kind of kernel. :P

02:23 <naobsd_> I don't think Rockchip kernel follows any standard ;)

02:23 <amstan> naobsd_: upstream does

02:24 <naobsd_> what I said is _Rockchip kernel_, not upstream

02:24 <naobsd_> my English is so wrong?

02:25 <naobsd_> I cannot count how many times I said "what I said is"...

02:25 <amstan> i would never use their 3.10 android kernel, when the upstream kernel works so well(at least for rk3288)

02:26 <naobsd_> many times I have to say same sentence 4 or 5 times in a short discussion :(

02:27 <Tony__> amstan, I just want to find a way likes the script ./scripts/checkpatch.pl in kernel.

02:27 <Tony__> to check my Android tree code style patch.

02:28 <amstan> Tony__: where are you sending that? and what patch is it?

02:29 <Tony__> the patch that I modified.

02:29 <Tony__> I think that which patch is not the point.

02:29 <Tony__> the _script_ is the point.

02:30 <amstan> it depends what kind aof patch it is, and what the people that you're sending it to like

02:31 <amstan> i'm still confused what repo it is, or why checkpatch.pl is not enough

02:31 <Tony__> amstan, checkpatch.pl can check java ?

02:32 <amstan> no, checkpatch.pl is only for kernel code for kernel code style

02:33 <Tony__> so it is not enough.

02:40 <Tony__> amstan, the tool lint you said is like ./scripts/checkpatch.pl ?

02:40 <naobsd_> Tony__: coding style is depend on project

02:40 <naobsd_> if your patch is for your project, follow your project rule

02:41 <amstan> and language, and developers that accept your patches(some are different than others)

02:41 <amstan> easiest is probably to ask the people you're sending patches to

02:41 <naobsd_> there is no general rule

02:42 <naobsd_> there might be common rule

02:42 <naobsd_> ask google for common one ;)

02:42 <naobsd_> e.g. there is "checkstyle" for eclipse

02:42 <Tony__> naobsd_, amstan checkpatch.pl is not only used to check the patch which is sent to somebody.

02:42 naobsd_ is now known as naobsd

02:43 <amstan> Tony__: how are you making a patch and not sending it to anyone?

02:43 <Tony__> I just want to check it when I run "git add/ commit"

02:43 <naobsd> Tony__: you can ignore checkpatch.pl if you won't send patches to upstream

02:44 <Tony__> amstan, naobsd my English is so wrong? Every time I can't speak out my _point_, or you can't get it!! :(

02:44 <naobsd> asking general rule for _all_ project on the net is pointless

02:45 <Tony__> I don't know why...

02:45 <naobsd> there is no general rule for private patch

02:45 <naobsd> you may follow any common rule

02:45 <amstan> Tony__: if you're sending your patch to somebody you need to ask them, otherwise it doesn't really matter, does it?

02:46 <naobsd> but we cannot enforce you to follow some specific rule w/o explicit goal

02:46 <amstan> if you want to feel good about yourself, ask the developers of that project anyway, even if you don't send them a patch

02:46 <amstan> naobsd: i agree

02:46 <Tony__> Yes, common rule.

02:48 <Tony__> okay, at first, I want to say that I didn't follow the common rule code style. I want to learn to do it.

02:48 <naobsd> it depends on project

02:48 <naobsd> it varies

02:49 <Tony__> in the kernel, when I modify something, before "git add/commit" I can use checkpatch.pl to check my modify if follow the common code style.

02:49 <naobsd> I don't know know all rules used in all project in AOSP or any other Android source tree

02:49 <naobsd> Tony__: yes, for kernel

02:50 <naobsd> and I don't know for other parts

02:52 <Tony__> naobsd, got it. My question was not specific enough.

02:54 <Tony__> naobsd, how about platform_frameworks_base ?

02:54 <Tony__> there are Cpp/Java languages.

02:54 <Tony__> https://github.com/android/platform_frameworks_base

02:55 <naobsd> it's a part of AOSP, but I don't know how AOSP reviews code style (I know about their gerrit, I don't know their review flow)

02:56 <naobsd> probably that page (amstan pointed) is their basic rule

02:57 <naobsd> but I don't know detail and I don't know they applies it strictly

03:01 <Tony__> naobsd, amstan thank you. And I finally put my clear description of the problem. ;)

03:02 <Tony__> I will check the lint tool which is post by amstan .

03:04 levd has joined #linux-rockchip

03:05 <Tony__> oh, I saw "In addition to testing that your ___Android application___ meets its functional requirements," I think its not suit me.

03:06 levd1 has quit [Ping timeout: 265 seconds]

03:10 <Tony__> naobsd, And how do you check it ? only in the mind ? ;)

03:10 RayFlower has quit [Read error: Connection reset by peer]

03:10 RayFlower has joined #linux-rockchip

03:11 <Tony__> (I'm not talking about kernel, I know how to check it in kernel.)

03:13 RayFlower has quit [Read error: Connection reset by peer]

03:13 RayFlower has joined #linux-rockchip

03:15 levd1 has joined #linux-rockchip

03:18 levd has quit [Ping timeout: 265 seconds]

03:19 <naobsd> cnxsoft: ping

03:20 <cnxsoft> hi

03:21 <Tony__> cnxsoft, hi.

03:24 <naobsd> we can use here too for discussion ;)

03:25 <naobsd> (if/when it's needed)

03:30 <cnxsoft> OK :)

03:31 <cnxsoft> So If I read correctly RK3188 boot code will look for the SD card first, then the eMMC.

03:31 <cnxsoft> But RK3288 will check the eMMC, before the SD card. Is that correct?

03:33 <Tony__> I don't know, but I think that is a good idea.

03:34 <Tony__> Many times I reboot device forgot to remove sdcard.

03:35 <Tony__> then I system in the eMMC is disappeared.

03:35 <Tony__> then my system in the eMMC is disappeared.

03:35 <naobsd> I think no one confirm "RK3188 try SD card first, then eMMC"

03:36 <naobsd> only "RK3188 try SD card first, then _NAND_" is confirmed

03:36 <cnxsoft> Ah yes.. OK :)

03:36 <naobsd> in this context, eMMC is not same as NAND

03:37 <naobsd> I guess RK3288 also does "try SD acrd, then NAND" but I don't have RK3288 with NAND

03:37 <cnxsoft> So that means RK3188 devices can't be bricked, but RK3288 devices could.

03:37 <naobsd> no, RK3188 can be bricked by same reason

03:38 <cnxsoft> Right, If they use NAND they can't be bricked, but if they use eMMC they could. (RK318)

03:41 naobsd_ has joined #linux-rockchip

03:41 <naobsd_> but I'm sure

03:41 <naobsd_> it's very rare

03:41 <naobsd_> for example, ASUS MeMO Pad 8 ME180A and MeMO Pad 10 ME102A (both RK3188) use special loader

03:42 naobsd has quit [Ping timeout: 246 seconds]

03:44 <naobsd_> chipspark's rayeager px2 board also uses special loader (it may be just "it's for px2, px2 is not same as rk3066")

03:44 naobsd_ is now known as naobsd

03:47 <Tony__> naobsd, I think I can confirm "RK3188 try SD card first, then eMMC".

03:48 <Tony__> because there are some doc of RK said that.

03:49 <naobsd> oh, do you rely RK docs?

03:49 <naobsd> ;)

03:49 <Tony__> SD Card Boot User Guide V1.1 20130124.pdf

03:50 <Tony__> And my experience. it's true.

03:51 <naobsd> I think I only read SD tool doc in chinese

03:51 <naobsd> maybe it's different doc

03:51 <naobsd> ah, you have RK3188 eMMC board, I remember

03:51 <naobsd> then surely confirmed

03:51 <naobsd> thank for the info :)

03:52 <naobsd> actually ASUS MeMO Pad 8 uses eMMC

03:52 <Tony__> http://translate.google.cn/?hl=zh-CN&client=aff-9991&channel=link&tab=wT#zh-CN/en/6.1.%20%E5%A6%82%E4%BD%95%E4%BB%8E%20sd%20%E5%8D%A1%E5%90%AF%E5%8A%A8%0A%E5%AF%B9%E4%BA%8E%202928%20%E8%8A%AF%E7%89%87%E9%9C%80%E8%A6%81%20flash%20%E6%98%AF%E7%A9%BA%E7%9A%84%E6%83%85%E5%86%B5%20maskrom%20%E6%89%8D%E4%BB%8E%20sd%20%E5%8D%A1%E5%90%AF%E5%8A%A8%2C%E6%89%80%E4%BB%A5%E5%A6%82%E6%9E%9C%E6%9C%BA%E5%99%A8%E5%B7%B2%E7%BB%8F%E7%83%A7%E4%BA%86%E5%9B%BA%E4%BB%B6

03:52 <Tony__> %2C%E9%9C%80%E8%A6%81%E7%9F%AD%E6%8E%A5%20flash%20%E5%9C%A8%20maskrom%20%E7%8A%B6%E6%80%81%E4%B8%8B%E4%BD%BF%E7%94%A8%E7%83%A7%E5%86%99%E5%B7%A5%E5%85%B7%E6%93%A6%E9%99%A4%20idb%20%E6%89%8D%E8%83%BD%E6%AD%A3%E5%B8%B8%E4%BB%8E%20sd%20%E5%BC%95%E5%AF%BC%E5%90%AF%E5%8A%A8%E3%80%82%E5%90%8E%E7%BB%AD%E7%9A%84%E8%8A%AF%E7%89%87%E5%B0%86%E9%BB%98%E8%AE%A4%E8%AF%86%E5%88%AB%E5%88%B0%E9%87%8F%E4%BA%A7%20sd%20%E5%8D%A1%E5%B0%B1%E7%AB%8B%E5%8D%B3%E4%BB%8E%20

03:52 <Tony__> sd%20%E5%8D%A1%E5%90%AF%E5%8A%A8%2C%E9%81%BF%E5%85%8D%E4%B8%8A%E8%BF%B0%E9%BA%BB%E7%83%A6%E7%9A%84%E6%93%8D%E4%BD%9C%E3%80%82

03:52 <naobsd> but I cannot find DDR blob and loader binary in eMMC

03:52 <naobsd> I guess it uses SPI

03:53 <Tony__> I say it again. "after 2928, the chip will boot first from sdcard if the sdcard is boot enable"

03:54 <naobsd> lol

03:55 <naobsd> RK3288 is not "after 2928"? ;)

03:55 <Tony__> I think it is.

03:55 <Tony__> RK3xxx > RK2xxx

03:55 <naobsd> but it boots eMMC first

03:56 <naobsd> it's not true

03:56 <naobsd> e.g. RK3066 is older than RK292x

03:56 <Tony__> my device it's boot from sdcard if it's enable.

03:56 <naobsd> I think RK3188, RK302x and RK292x is same generation

03:56 <Tony__> RK3188.

03:56 <naobsd> not sure

03:57 <naobsd> yes, I said thank you

03:57 <naobsd> I just don't believe docs

03:57 <Tony__> Yes, we shouldn't believe docs. :P

03:58 <Tony__> always.

03:58 <naobsd> do you know anything about boot from SPI NOR?

03:58 <naobsd> it's documented but I never seen/confirmed real device

03:59 <Tony__> naobsd, sorry, I haven't try boot from SPI NOR. :(

03:59 <Tony__> on rk3188.

03:59 <naobsd> I see, thanks anyway

04:00 <Tony__> And I have try boot from NOR with other chip such as samsung's S3C2440.

04:01 <Tony__> Nowadays, nobody want to use NOR. I just guess. ;)

04:07 <naobsd> some system which runs boot code on ROM uses NOR

04:08 <naobsd> I'm not hardware guy but

04:08 <naobsd> serial interface is preferred now

04:08 <naobsd> I guess.

04:09 <naobsd> serial -> low pin count

04:11 <Tony__> naobsd, Agreed.

04:12 <Tony__> You said the RK3288 just now, I think they change the rule again after RK3188. ;)

04:14 <Tony__> first boot from SDCARD is dangerous. It's a bug in my opinion. I

04:16 levd has joined #linux-rockchip

04:18 <naobsd> Tony__: http://www.oracle.com/technetwork/articles/javase/codeconvtoc-136057.html just FYI

04:19 levd1 has quit [Ping timeout: 264 seconds]

04:20 <naobsd> SD card, external source, may be unreliable as a "1st" (logically/physically/electrically)

04:28 Astralix has joined #linux-rockchip

04:30 Astralix1 has quit [Ping timeout: 250 seconds]

04:31 GriefNorth has joined #linux-rockchip

04:58 levd1 has joined #linux-rockchip

05:00 levd has quit [Ping timeout: 245 seconds]

05:06 RayFlower has quit [Read error: Connection reset by peer]

05:07 RayFlower has joined #linux-rockchip

05:11 RayFlower has quit [Read error: Connection reset by peer]

05:12 RayFlower has joined #linux-rockchip

05:16 RayFlower has quit [Read error: Connection reset by peer]

05:17 RayFlower has joined #linux-rockchip

05:18 levd has joined #linux-rockchip

05:20 levd1 has quit [Ping timeout: 244 seconds]

05:22 RayFlower has quit [Read error: Connection reset by peer]

05:22 RayFlower has joined #linux-rockchip

06:03 levd1 has joined #linux-rockchip

06:05 <Tony__> thank you.

06:05 levd has quit [Ping timeout: 250 seconds]

06:08 RayFlower has quit [Read error: Connection reset by peer]

06:08 RayFlower has joined #linux-rockchip

06:43 RayFlower has quit [Read error: Connection reset by peer]

06:44 RayFlower has joined #linux-rockchip

06:48 RayFlower has quit [Read error: Connection reset by peer]

06:49 RayFlower has joined #linux-rockchip

07:10 levd has joined #linux-rockchip

07:13 levd1 has quit [Ping timeout: 250 seconds]

07:16 kurain has joined #linux-rockchip

07:25 levd1 has joined #linux-rockchip

07:27 levd has quit [Ping timeout: 252 seconds]

07:46 levd1 has quit [Remote host closed the connection]

07:46 levd has joined #linux-rockchip

08:08 RayFlower has quit [Read error: Connection reset by peer]

08:08 RayFlower has joined #linux-rockchip

08:10 levd has quit [Remote host closed the connection]

08:10 levd has joined #linux-rockchip

08:12 RayFlower has quit [Read error: Connection reset by peer]

08:13 RayFlower has joined #linux-rockchip

08:17 AstralixNB has joined #linux-rockchip

08:20 <rperier> hi all

08:21 levd has quit [Remote host closed the connection]

08:21 levd has joined #linux-rockchip

08:28 antoinemaillard has joined #linux-rockchip

08:29 <naobsd> hi

08:33 <rperier> sent an email to linux-rockchip, several regressions detected

08:36 <naobsd> how about

08:36 <naobsd> uploading kernel binary to test

08:37 <naobsd> well

08:38 <naobsd> is build & test vanilla linux-next useful ?

08:39 <naobsd> mmm

08:39 <naobsd> is build & upload vanilla linux-next useful for testing?

08:49 kurain1 has joined #linux-rockchip

08:50 kurain has quit [Ping timeout: 244 seconds]

08:52 <rperier> naobsd: yes it is, this is the code which will be merged onto the Linus's tree and which will be contained in -rcX, code base that most of developer will be used as workspace

08:53 <rperier> this is a good way to detect bugs early

08:53 eebrah_ has quit [Quit: leaving]

08:53 <rperier> and detect collisions and regressions (directly or indirectly)

08:53 eebrah has quit [Remote host closed the connection]

08:54 eebrah has joined #linux-rockchip

08:56 <naobsd> is multi_v7_defconfig usable?

09:04 eebrah has quit [Quit: leaving]

09:04 eebrah has joined #linux-rockchip

09:05 levd has quit [Remote host closed the connection]

09:05 levd has joined #linux-rockchip

09:05 AstralixNB1 has joined #linux-rockchip

09:06 naobsd has quit [Ping timeout: 246 seconds]

09:07 AstralixNB has quit [Ping timeout: 250 seconds]

09:25 AstralixNB1 has quit [Quit: Leaving.]

09:26 antoinemaillard has quit [Quit: antoinemaillard]

09:30 RayFlower has quit [Read error: Connection reset by peer]

09:31 RayFlower has joined #linux-rockchip

09:32 naobsd has joined #linux-rockchip

09:33 <rperier> naobsd: I use rk31_rk30_defconfig from Heiko's repo personnally

09:35 <naobsd> yes I know that, I just want to know about multi_v7_defconfig

09:35 <naobsd> probably it will not be enough to test all things

09:35 antoinemaillard has joined #linux-rockchip

09:35 <naobsd> all rk things

09:35 <naobsd> then should we add rk things to multi_v7_defconfig?

09:37 <naobsd> hm

09:37 <naobsd> ok, let's forget it

09:37 AstralixNB has joined #linux-rockchip

09:44 RayFlower has quit [Read error: Connection reset by peer]

09:45 RayFlower has joined #linux-rockchip

09:58 levd1 has joined #linux-rockchip

10:00 levd has quit [Ping timeout: 250 seconds]

10:04 wildea01 has joined #linux-rockchip

10:04 naobsd has quit [Quit: Page closed]

10:09 Tony__ has quit [Remote host closed the connection]

10:15 levd has joined #linux-rockchip

10:17 levd1 has quit [Ping timeout: 245 seconds]

10:25 RayFlower has quit [Read error: Connection reset by peer]

10:26 RayFlower has joined #linux-rockchip

10:41 levd has quit [Ping timeout: 245 seconds]

10:53 RayFlower has quit [Read error: Connection reset by peer]

10:53 RayFlower has joined #linux-rockchip

10:57 RayFlower has quit [Read error: Connection reset by peer]

10:58 RayFlower has joined #linux-rockchip

11:02 RayFlower has quit [Read error: Connection reset by peer]

11:03 RayFlower has joined #linux-rockchip

11:14 antoinemaillard has quit [Quit: antoinemaillard]

11:16 eebrah has quit [Quit: Lost terminal]

11:20 RayFlower has quit [Read error: Connection reset by peer]

11:21 RayFlower has joined #linux-rockchip

11:27 RayFlower has quit [Read error: Connection reset by peer]

11:28 RayFlower has joined #linux-rockchip

11:30 antoinemaillard has joined #linux-rockchip

11:40 antoinemaillard has quit [Quit: antoinemaillard]

11:40 RayFlower has quit [Read error: Connection reset by peer]

11:41 RayFlower has joined #linux-rockchip

11:44 naobsd has joined #linux-rockchip

11:51 RayFlower has quit [Read error: Connection reset by peer]

11:52 RayFlower has joined #linux-rockchip

12:06 antoinemaillard has joined #linux-rockchip

12:07 Dumonde has joined #linux-rockchip

12:08 antoinemaillard has quit [Client Quit]

12:10 antoinemaillard has joined #linux-rockchip

12:11 Dumonde has quit [Quit: Ухожу я от вас (xchat 2.4.5 или старше)]

12:21 RayFlower has quit [Read error: Connection reset by peer]

12:22 RayFlower has joined #linux-rockchip

12:24 RayFlower has quit [Read error: Connection reset by peer]

12:25 RayFlower has joined #linux-rockchip

12:34 RayFlower has quit [Read error: Connection reset by peer]

12:35 RayFlower has joined #linux-rockchip

12:35 nighty-_ has joined #linux-rockchip

12:46 antoinemaillard has quit [Quit: antoinemaillard]

12:47 antoinemaillard has joined #linux-rockchip

12:49 Omegamoon has quit [Ping timeout: 244 seconds]

12:54 RayFlower has quit [Read error: Connection reset by peer]

12:54 RayFlower has joined #linux-rockchip

12:56 RayFlower has quit [Read error: Connection reset by peer]

12:57 RayFlower has joined #linux-rockchip

13:18 antoinemaillard has quit [Quit: antoinemaillard]

13:22 RayFlower has quit [Read error: Connection reset by peer]

13:23 RayFlower has joined #linux-rockchip

13:32 <rperier> mmind00: hi, I think that what rockchip sent for phy usb driver might be more generic , we might use the same driver for all SoCs, no ?

13:33 <mmind00> rperier: yep, the principle is the same for all, only the bits / register offsets differ

13:34 <mmind00> rperier: so I'd let this land as is and then extend it with the data for the other socs

13:34 <rperier> so I will ask him to make the driver a bit more generic for that

13:34 <rperier> mmind00: oh really ?

13:34 antoinemaillard has joined #linux-rockchip

13:34 <rperier> mmind00: you mean, we might ask the required data structure and adapt the code when we will need changes for older SoCs...

13:34 <rperier> s/ask/add/

13:35 <mmind00> rperier: correct

13:35 <rperier> yes, we could... So I won't talk about this part in my review in this case (I have some remarks)

13:36 <rperier> :)

13:36 Omegamoon has joined #linux-rockchip

13:37 <mmind00> rperier: great :-)

13:39 <rperier> that's important to help to reviews some stuffs too ;)

13:41 antoinemaillard has quit [Quit: antoinemaillard]

13:41 <mmind00> rperier: yep ... and one learns quite a lot ... i.e. I've gotten quite a bit better at reviewing stuff (and not only developing it) since this flood started :-)

13:43 kurain1 has quit [Remote host closed the connection]

13:44 antoinemaillard has joined #linux-rockchip

13:46 antoinemaillard has quit [Client Quit]

13:47 GriefNorth has quit [Quit: WeeChat 1.0.1]

13:51 RayFlower has quit [Read error: Connection reset by peer]

13:51 RayFlower has joined #linux-rockchip

13:51 antoinemaillard has joined #linux-rockchip

13:52 <rperier> mmind00: yeah that's good to learn things too, I totally agree. That's important to read code from other in the kernel, you learn good and bad practices

13:53 Omegamoon has quit [Ping timeout: 255 seconds]

13:55 <rperier> mmind00: btw, how would you debug an ethernet issue on a board with the linux kernel ? (the ethernet is completly dead with "next"). Do you know useful kernel tools/cmdline options for that ? I planned to use ethtool for a start... uart... debugfs and... that's all I can do, I think...

13:56 <mmind00> rperier: git bisect is the weapon of choice if it worked in the past, but does not now anymore

13:56 <rperier> I need to find some technical articles or conference presentations about advanced kernel debugging, I think

13:57 <mmind00> rperier: nope, at first you only need to find the commit introducing the problem

13:57 <rperier> problem bing that "bisect" itself is a nightmare with linux-next, there are a tons of merge commits... so when you bisect a merge commit, you bisect a tons of commits with it :/

13:57 <rperier> mhhh ok

13:58 <rperier> (there are probably useful options for this case, I will investigate)

13:59 <mmind00> rperier: btw how "dead" is the ethernet? I.e. is the phy still recognized?

13:59 <rperier> yes it is

13:59 cnxsoft1 has joined #linux-rockchip

13:59 <rperier> the driver is connected to the phy

13:59 <rperier> eth0 exists

13:59 <rperier> dhcpc -n -i eth0 does not work (never gets an IP), ping does not work with an static IP address

14:00 <rperier> interface is up when I plug an ethernet cable, it is down when I unplug it...

14:01 <rperier> clocks are good...

14:01 cnxsoft has quit [Ping timeout: 256 seconds]

14:02 ganbold_ has quit [Ping timeout: 255 seconds]

14:02 <mmind00> rperier: can you try doing a "git revert 78eaf6095cc763c1a228ebac5682852f04e85205" ... https://git.linaro.org/people/mike.turquette/linux.git/commitdiff/78eaf6095cc763c1a228ebac5682852f04e85205 is the one commit on the rockchip side that has a slight possibility of being the cause

14:02 dlezcano has joined #linux-rockchip

14:06 <rperier> yes I already started to bisect things in clk and pinctrl

14:06 <rperier> mmind00: I will test this evening

14:06 <rperier> (I have not my board at work)

14:10 <rperier> the commit is from 4 Nov... I found regressions from 21 Nov... I will test anyway, but not sure that this is the commit which introduced regression

14:13 <rperier> (well perhaps it was merged recently onto linux-next.. the date is not really objective here)

14:14 cnxsoft1 has quit [Quit: cnxsoft1]

14:18 antoinemaillard has quit [Quit: antoinemaillard]

14:21 antoinemaillard has joined #linux-rockchip

15:26 RayFlower has quit [Read error: Connection reset by peer]

15:26 RayFlower has joined #linux-rockchip

15:28 RayFlower has quit [Read error: Connection reset by peer]

15:29 RayFlower has joined #linux-rockchip

15:41 RayFlower has quit [Read error: Connection reset by peer]

15:42 RayFlower has joined #linux-rockchip

15:44 benja`_ is now known as benja

15:55 RayFlower has quit [Read error: Connection reset by peer]

15:55 RayFlower has joined #linux-rockchip

16:14 RayFlower has quit [Read error: Connection reset by peer]

16:14 RayFlower has joined #linux-rockchip

16:20 RayFlower has quit [Read error: Connection reset by peer]

16:20 RayFlower has joined #linux-rockchip

16:51 RayFlower has quit [Read error: Connection reset by peer]

16:51 RayFlower has joined #linux-rockchip

17:06 Omegamoon has joined #linux-rockchip

17:09 AstralixNB has quit [Ping timeout: 250 seconds]

17:11 Omegamoon has quit [Ping timeout: 264 seconds]

17:12 dlezcano has quit [Quit: Leaving]

17:35 RayFlower has quit [Read error: Connection reset by peer]

17:35 RayFlower has joined #linux-rockchip

17:42 RayFlower has quit [Read error: Connection reset by peer]

17:42 RayFlower has joined #linux-rockchip

17:52 RayFlower has quit [Read error: Connection reset by peer]

17:53 RayFlower has joined #linux-rockchip

17:54 eebrah has joined #linux-rockchip

18:04 benja is now known as benja`

18:14 wildea01 has quit [Quit: leaving]

18:18 antoinemaillard has quit [Quit: antoinemaillard]

18:18 naobsd has quit [Ping timeout: 246 seconds]

18:34 RayFlower has quit [Read error: Connection reset by peer]

18:34 RayFlower has joined #linux-rockchip

18:45 <rperier> mmind00: you was right, reverting this commit fixes the issue for ethernet

18:46 <rperier> mmind00: I will propose a proper fix

18:46 <rperier> (at least I will try as I did not touch to clk yet, but I am opened to suggestions during review)

18:46 <rperier> good catch

19:05 RayFlower has quit [Read error: Connection reset by peer]

19:05 RayFlower has joined #linux-rockchip

19:12 RayFlower has quit [Read error: Connection reset by peer]

19:12 RayFlower has joined #linux-rockchip

19:19 <mmind00> rperier: great ... ideally you could try to identify the clock that gets turned off and disables the emac functionality

19:22 RayFlower has quit [Read error: Connection reset by peer]

19:23 RayFlower has joined #linux-rockchip

19:46 benja` is now known as benja

19:58 <rperier> mmind00: this is what I will do yes

20:32 benja is now known as benja`

20:35 RayFlower has quit [Read error: Connection reset by peer]

20:35 RayFlower has joined #linux-rockchip

21:04 FreezingCold has quit [Ping timeout: 264 seconds]

21:12 field^Mop has joined #linux-rockchip

21:15 AstralixNB has joined #linux-rockchip

21:17 AstralixNB1 has joined #linux-rockchip

21:19 AstralixNB has quit [Ping timeout: 250 seconds]

21:23 RayFlower has quit [Read error: Connection reset by peer]

21:24 RayFlower has joined #linux-rockchip

21:38 RayFlower has quit [Read error: Connection reset by peer]

21:38 RayFlower has joined #linux-rockchip

21:39 <field^Mop> naobsd: ping

21:39 <field^Mop> anyone: ping

21:40 <field^Mop> well..

21:40 <field^Mop> what is the abbreviation IDB? and what does it mean?

22:27 RayFlower has quit [Read error: Connection reset by peer]

22:27 RayFlower has joined #linux-rockchip

22:31 akaizen_ has quit [Remote host closed the connection]

22:32 akaizen has joined #linux-rockchip

22:36 RayFlower has quit [Read error: Connection reset by peer]

22:36 RayFlower has joined #linux-rockchip

22:38 nighty-_ has quit [Quit: Disappears in a puff of smoke]

22:45 RayFlower has quit [Read error: Connection reset by peer]

22:45 RayFlower has joined #linux-rockchip

22:59 akaizen_ has joined #linux-rockchip

23:02 akaizen_ has quit [Read error: Connection reset by peer]

23:02 akaizen has quit [Ping timeout: 258 seconds]

23:02 akaizen_ has joined #linux-rockchip

23:03 <amstan> mmind00: https://chromium-review.googlesource.com/#/c/233691/

23:03 <amstan> mmind00: seems like addy's broken dto fix is not complete

23:05 AstralixNB1 has quit [Ping timeout: 250 seconds]

23:08 RayFlower has quit [Read error: Connection reset by peer]

23:08 RayFlower has joined #linux-rockchip

23:21 field^Mop has quit [Ping timeout: 272 seconds]