00:20 <khilman> xdarklight: from gxbb-p200: http://termbin.com/m5rb

00:20 <khilman> sorry for the screwy output due to terminal colors/tab-completion etc.

00:20 <khilman> but the data you need should be there

01:38 <Guest86765> Minere BTC enquanto navega e trabalha sem deixar o pc lentão e economizando energia obs: so funciona no Google Chrome do pc. https://getcryptotab.com/718967 Video tutorial https://www.youtube.com/watch?v=luzqQN3kL4g&t=166s

07:35 <xdarklight> khilman: thanks!

08:36 <lissyx> narmstrong, I'm getting a new board to replace the faulty one

15:11 <webczat> and again, is there any reason as to why there is no support for environment on emmc on uboot?

16:46 <afaerber> webczat, I guess someone just needs to implement it - would you be willing to?

16:48 <webczat> afaerber: well I would rather have problems implementing things I do not understand. like from what I can see it only requires some defines?

16:51 <webczat> oh also btw how do i know which pin is which? there is a table on odroid c2 wiki, but it is not compatible with mainline kernel naming and stuff. not quite sure how would I go about mapping between these

16:52 <afaerber> haven't needed it myself, so not sure if driver is prepared, but yes, there will be a few defines for eMMC env presence and location

17:02 <afaerber> (or possibly Kconfig settings these days?)

17:02 <webczat> not sure

17:03 <webczat> heard that nope

17:05 <webczat> what about pin stuff?

17:10 <lvrp16> webczat: or you can just create a FAT partition and have u-boot load/save env to that

17:10 <webczat> o rly? can it even do that?

17:11 <lvrp16> mainline u-boot definitely can

17:14 <webczat> does that include stuff like boot delays?

17:16 <lvrp16> boot delay is programmable, you can just change a define

17:17 <webczat> yes. but i may want to set it without recompile

18:57 <webczat> and for curiosity how do you enable adc? i don't understand much but I do not see adc pins in dtb

19:09 <xdarklight> webczat: loook at meson-gxbb-nanopi-k2.dts and use it as reference

19:09 <xdarklight> webczat: the ADC pins are not in the dts/dtb because the ADC pins are not configurable (they're fixed, always routed to the ADC and cannot be used for anything else)

19:10 <webczat> like you just enable saradc

19:10 <webczat> i mean, set status to enabled and be done with it?

19:12 <xdarklight> you also need to specify a 1.8V regulator as voltage reference

19:12 <xdarklight> but that's it

19:13 <webczat> well.

19:13 <xdarklight> (I just checked Odroid-C2 schematics: it routes VDDIO_AO1V8 to pin 38 on the header, VDDIO_AO1V8 itself is provided by a fixed regulator just like on the nanopi k2)

19:13 <webczat> I do not need this actually. what I am trying to do is understanding things like mapping between stuff in upstream and in amlogic/hardkernel kernel. especially that I am not into electronics at present and may have difficulties

19:14 <webczat> like the topic interests me, the problem is mostly understanding stuff. including basics

19:15 <xdarklight> OK, if you want to use it in real life then you need the voltage reference though (it's mandatory per device tree bindings and the driver will not load if it's missing: https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/iio/adc/amlogic%2Cmeson-saradc.txt )

19:17 <webczat> well i know enough to know that I need voltage reference. :) just didn't know i have to specify it, but my actual question is about mapping everything from one kernel to another, as in, names differ. so adc, i2c, uart... which is which and how do I know...

19:19 <webczat> adc made me wonder only because I thought I saw all pins in the gpio controller line names for c2, but there was no pinmux block for adc.

19:24 <webczat> xdarklight: like i thought that those pins marked j2 pin number are all on the header, + all 4 i2c pins, + 2 pwm pins, and + 5v, 3.3v gnd and 1.8v reference pins, that gave 40. is adc specified there even though it cannot be used as gpio? or I misunderstand?

19:30 <webczat> ah, I believe those p2m's are not those exposed?

19:31 <webczat> *pwm's

19:31 <webczat> but then for example why both i2c's are marked as i2c and stuff like potential pwms/uarts are marked by their pin numbers... seems weird to me

20:36 <xdarklight> webczat: well, there are more pins one header which cannot be used as GPIOs: 5V0, 3V3, GND, the ADC pins, ...

20:37 <xdarklight> webczat: regarding the naming: I have no idea why hardkernel labeled them this way