| 00:14.55 | *** join/#cubieboard ttmrichter (~ttmrichte@111.4.119.28) |
| 00:17.16 | *** join/#cubieboard des2 (~des2@pool-71-190-37-7.nycmny.east.verizon.net) |
| 00:33.57 | zindello | Is there anyone from cubieboard online atm? |
| 00:52.13 | *** join/#cubieboard spm_Draget (~quassel@ip-178-201-74-115.unitymediagroup.de) |
| 01:06.47 | *** join/#cubieboard MuNk` (~NOP@2001:470:1f09:1ec1:210:75ff:fe1a:bdb0) |
| 01:50.21 | *** join/#cubieboard itamarjp (~itamar@fedora/itamarjp) |
| 01:50.28 | hno | zindello, nope |
| 02:19.55 | *** join/#cubieboard itamarjp (~itamar@177.106.215.177) |
| 02:19.55 | *** join/#cubieboard itamarjp (~itamar@fedora/itamarjp) |
| 04:12.14 | *** join/#cubieboard [1]des2 (~des2@pool-96-232-65-112.nycmny.east.verizon.net) |
| 04:14.25 | *** join/#cubieboard ttmrichter (~ttmrichte@113.106.102.174) |
| 05:47.15 | *** join/#cubieboard [1]des2 (~des2@pool-96-232-65-250.nycmny.east.verizon.net) |
| 05:51.43 | *** join/#cubieboard rvalles (~rvalles@unaffiliated/rvalles) |
| 06:02.48 | *** join/#cubieboard rvalles (~rvalles@unaffiliated/rvalles) |
| 06:56.11 | mnemoc | moin |
| 07:10.39 | Peanut | moin moin |
| 07:23.14 | mase_wk | moin |
| 08:43.13 | *** join/#cubieboard hipboi (~hipboi@116.77.134.124) |
| 09:19.28 | *** join/#cubieboard unrest (~unrest_fr@199.193.249.14) |
| 09:19.33 | unrest | hi |
| 09:20.31 | *** join/#cubieboard Borgso (~nirox@unaffiliated/borgso) |
| 10:16.09 | *** join/#cubieboard arapaho (~arapaho@pierre.infomaniak.ch) |
| 10:37.23 | *** join/#cubieboard GeorgeH_work (~GeorgeH@75-150-151-121-Philadelphia.hfc.comcastbusiness.net) |
| 10:55.44 | mnemoc | hipboi: will the next batch be 2012-08-08 too? |
| 10:55.58 | hipboi | yes |
| 10:56.18 | hipboi | the pcb is already made |
| 11:06.03 | unrest | wonders if the cubieboard is suitable for OS development |
| 11:06.18 | unrest | wonders when/how to order as well |
| 11:08.27 | RaYmAn | unrest: it's possible to do JTAG on it, so it should be. Though - not a lot of stuff in the A10 is publicly documented, so it's probably an uphill battle |
| 11:09.06 | unrest | i'm better off with an arm9/arm11 then, i guess.. |
| 11:10.19 | RaYmAn | depends on purpose I guess - I mean, you can quite easily do basic OS dev on it =P Bare-metal programming and such |
| 11:10.30 | RaYmAn | but it gets harder once you enter graphics etc |
| 11:12.51 | unrest | bare metal's first, of course, but if i run into badly/undocumented hardware, it'll take the fun off it.. |
| 11:13.36 | unrest | creating a HAL and conforming to CMSIS, i'll be able to "easily" switch boards, once i run into such problems.. |
| 11:13.57 | unrest | nah.. that makes two (or more) boards and more spent money. |
| 11:14.11 | *** join/#cubieboard [1]des2 (~des2@pool-71-190-33-57.nycmny.east.verizon.net) |
| 11:14.45 | mnemoc | unrest: don't fear the lack of documentation, beside video decoding open A10 support isn't in that bad shape |
| 11:15.17 | mnemoc | it's still an amazing development board |
| 11:16.30 | RaYmAn | mnemoc: realisticly though, something with proper, public, documentation is better for bare metal/OS development :P |
| 11:16.38 | unrest | what makes it amazing (aside from it's cost)? |
| 11:16.51 | unrest | RaYmAn's right |
| 11:16.54 | RaYmAn | I mean, what you'll mostly have to do on a10 will be read through the open source kernel code and replicate it |
| 11:17.04 | unrest | :/ |
| 11:17.39 | mnemoc | yes, the best docu we have is the actual code :| |
| 11:17.54 | mnemoc | which is kind of hard to read |
| 11:17.56 | unrest | reality 1, cubieboard 0 |
| 11:18.01 | unrest | :| |
| 11:18.26 | RaYmAn | cubieboard is kind of cool though :D |
| 11:18.26 | mnemoc | that's the sad reality of cheap chinese socs indeed |
| 11:18.46 | RaYmAn | is definitely getting one when 1gb's are available again |
| 11:20.20 | *** join/#cubieboard [1]des2 (~des2@pool-71-190-38-177.nycmny.east.verizon.net) |
| 11:31.06 | lsoem | what modifications are planned for the next revision (RTC, I2S headers)? |
| 11:37.11 | mnemoc | i heared of eSATAp and the move of LCD to a separated LVDS header to be able to use those 40 pins in other A10 features (note they are already usable as GPIOs if LCD is not configured) |
| 11:42.25 | hipboi | rtc are in plan |
| 11:43.10 | *** join/#cubieboard hipboi_ (~hipboi@116.77.133.213) |
| 11:44.44 | lsoem | mnemoc: yeah I saw the datasheet, are the ports "fex configured"? |
| 11:45.12 | mnemoc | yes. and by default they are inputs |
| 12:18.08 | *** join/#cubieboard [1]des2 (~des2@pool-96-232-71-225.nycmny.east.verizon.net) |
| 12:37.49 | *** join/#cubieboard [1]des2 (~des2@pool-96-232-69-26.nycmny.east.verizon.net) |
| 12:53.54 | *** join/#cubieboard [1]des2 (~des2@pool-96-232-65-109.nycmny.east.verizon.net) |
| 13:29.48 | *** join/#cubieboard trinathon (~deans-and@128.187.220.201) |
| 13:41.14 | *** join/#cubieboard hno (~hno@squid/developer/hno) |
| 13:50.56 | *** join/#cubieboard trinathon (~deans-and@128.187.220.201) |
| 13:59.57 | *** join/#cubieboard kocka (~kocka@2a01:270:0:ffff:ffff:200c:0:2) |
| 13:59.59 | kocka | hoi |
| 14:21.23 | *** join/#cubieboard itamarjp (~itamar@fedora/itamarjp) |
| 14:51.51 | *** join/#cubieboard trinathon (~deans-and@128.187.220.201) |
| 15:09.06 | GeorgeH_work | Hey all, anyone have a cubieboard yet? |
| 15:31.03 | mnemoc | GeorgeH_work: not yet. |
| 15:40.43 | *** join/#cubieboard Peanut (boven@loopy.jive.nl) |
| 15:50.38 | *** join/#cubieboard [1]des2 (~des2@pool-96-232-70-102.nycmny.east.verizon.net) |
| 15:52.38 | *** join/#cubieboard des2 (~des2@pool-71-190-35-31.nycmny.east.verizon.net) |
| 16:41.11 | *** join/#cubieboard trinathon (~deans-and@128.187.220.201) |
| 17:21.39 | *** join/#cubieboard [1]des2 (~des2@pool-71-190-43-156.nycmny.east.verizon.net) |
| 21:05.33 | *** join/#cubieboard ibot (~ibot@rikers.org) |
| 21:05.33 | *** topic/#cubieboard is http://cubieboard.org - http://linux-sunxi.org/Cubieboard - logs: http://ibot.rikers.org/%23cubieboard/ |
| 22:04.55 | *** join/#cubieboard hiredman (~hiredman@ip67-152-53-125.z53-152-67.customer.algx.net) |
| 22:19.46 | *** join/#cubieboard zindello (~zindello@ppp59-167-177-16.static.internode.on.net) |
| 22:22.14 | hiredman | I've noticed http://linux-sunxi.org/Cubieboard doesn't list any of the pins as "gpio", does that mean none of the ports can be used easily for setting the voltage on a wire high or low? |
| 22:23.00 | zindello | There was some discussion on the mailing list about this a few days ago |
| 22:23.19 | hiredman | ah, I just joined the list |
| 22:23.22 | zindello | From what I understand, most of those pins are just GPIO pins that are multiplexed, and those listings are the multiplex functions for the pins |
| 22:23.51 | zindello | Although exactly which pins are GPIO/Multiplexed and which are dedicated pins are yet to be announced |
| 22:24.29 | hiredman | I see |
| 22:35.55 | mnemoc | mostly only the VCCs and Grounds aren't GPIOs by the default ;-) |
| 22:36.26 | mnemoc | from those on the headers I mean |
| 22:37.30 | mnemoc | I've been adding links to A10/PIO of each pin in http://linux-sunxi.org/Cubieboard#Expansion_ports |
| 22:37.40 | mnemoc | but it's pretty boring :| |
| 22:37.49 | mnemoc | so it moves slowly |
| 22:38.40 | mnemoc | in A10/PIO all pins saying type I/O means they are input when MUX 0 and output when MUX 1 |
| 22:40.21 | mnemoc | A10/PIO also needs to be completed. info comes from schematics, the a10 datasheet and sample .fex files |
| 22:40.30 | mnemoc | help welcomed |
| 22:44.35 | mnemoc | good night |
| 23:17.11 | *** join/#cubieboard remi_ (~remi@adsl.absurde.org) |
| 23:40.29 | *** join/#cubieboard ttmrichter (~ttmrichte@113.106.102.172) |