00:21 <bashintosh> amstan: sorry to drop in - no luck with the archlinux toolchain :( Exactly the same error: https://paste.fedoraproject.org/244441/ Definitely not a toolchain issue at this point. I can try to add the prototypes for those functions and see what happens but I feel like it should just build as it is.. Mmh, strange really.

06:37 <rperier> hi all

07:38 <rperier> mhhh veyron based boards are already in mainline... very interesting... I will work on adding a dts for rk3288-speedy in mainline, I think (I will need one to work on wifi)

08:08 <mmind00> rperier: didn't you have the hisense chromebook? [jerry]

08:10 <cristian_c> hello

08:11 <cristian_c> I've tried gpiodump. I loaded the kernel module and I've checked all the pins, in three modes but I'd like to know what to do in order to make things working. Any ideas?

08:26 <rperier> mmind00: no, It was not possible for me to buy one, so I bought an asus c201 (speedy) , which is very nice too

08:27 <mmind00> great then ... spreading different machines helps testing :-)

08:29 <cristian_c> another question

08:29 <cristian_c> I'd like to access to mount user readable/writable nand partition (i.e. /sdcard)

08:30 <cristian_c> I think loop* block files are related to mtd partitions and I think I could mount /system or /sdcard , mtdblock8 and mtdblock9, respectively (they are ext4 the first one and vfat the second one). So, I'd like to know if maybe I've to enable some CONFIG options in the kernel configuration file or to something else. Any ideas?

08:36 <rperier> mmind00: exactly !

08:36 <rperier> in the future days, I should send an dts for speedy and for the radxa rock 2 , I have received my rock 2 too :)

08:37 <naobsd> is there rk3288 chromebook "product name <-> code name" info?

08:42 <rperier> unfortunately, that's not documented in doc/dt-bindings/arm/rockchip.txt in the chromeos kernel :/

08:55 <cristian_c> another question

08:57 <cristian_c> if I connect usb optical drive and I put a disc into it, it's partially mounted: its labelbappears in my file manager

08:58 <cristian_c> and I can also eject it from my file manager

08:59 <rperier> amstan: hi, do you know if there is a mapping somewhere for "product name" <-> "code name" ?

08:59 <rperier> that's not written in dts files in chromeos kernel or documented in doc/dt-bindings/arm/rockchip.txt

09:00 <cristian_c> but if I try to mount the media i get an error message windows, that says: Error mounting /dev/sr0 at /media...

09:03 <cristian_c> Command line mount -t iso9660 -o uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500 /dev/sr0 /media

09:06 <cristian_c> exited with non-zero exit status 32: mount: block device /dev/sr0 is write-protected, mounting read-only

09:07 <cristian_c> mount: wrong fs type, bad option bad superblock on /dev/sr0, missing codepage or helper program, or other error

09:08 <cristian_c> In some cases useful info is found in syslog - try dmesg | tail or so

09:19 <cristian_c> I've looked at dmesg

09:20 <cristian_c> but it seems there is no useful info

09:23 <cristian_c> How can I mount properly the media disc? Any ideas?

09:24 <cristian_c> I should enable some additional options in kernel .config file?

09:24 <cristian_c> *should I

10:03 <mmind00> rperier (and amstan): http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices but that is currently still missing the veyron devices

10:03 <mmind00> ah sorry, I meant naobsd

14:26 <bardolomejus> Hello, anybody home?

17:44 <amstan> rperier: speedy=asus c201, minnie=asus c100(flip), jerry=hisense(walmart only), jaq=haier(amazon), mighty=haier edu

17:47 <mmind00> amstan: somebody should update that page on chromium.org ;-)

17:47 <amstan> "somebody", lol

17:56 <mmind00> oh "somebody" just did ;-)

17:56 <amstan> i'll give it to someone else to format it more

23:27 <steev> what page

23:37 <mmind00> steev: http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices

23:38 <steev> this plane's wifi SUUUUUCKS