arm-netbook October 2013

arm-netbook@lists.phcomp.co.uk

23 participants
37 discussions

Chinese SoC vendor striving for world domination? Show your GPL loyalty page or get out of business!
by Paul Sokolovsky 06 Oct '13

06 Oct '13

Hello, I don't know if other folks noticed that already, but by now almost all Chinese ARM SoC vendors (targetting mass consumer market) put up some kind of "GPL/FOSS loyalty" page - and sources. I specifically call that "GPL loyalty" because as we know, there's some road ahead (maybe long) before it's "GPL compliance". Good news that some go beyond just GPL and provide Android sources, etc. It's yet to be seen how actually that useful technically as of now, but the talk about the outlook change. I'm sure that some of the vendors below did that because others did it. So, it looks like it gets self-sustaining, as put in subj: people come to you, and in quick chit-chat ask where's you GPL page, and if you say "nowhere", you get that strange look and people move to other booths, because Allwinner, Rockchip and everyone has it, and if you don't get that simple license thing, how you can actually hack on kernel and produce value? The list is: Telechips https://www.telechips.com/technical_support/kor/opensource/opensource_list.… Rockhip http://git.linux-rockchip.org/public/ Allwinner http://www.allwinnertech.com/en/awt/news/2013-04-23.html Amlogic http://openlinux.amlogic.com/ VIA/WondermediaLinux on small ARM machines <arm-netbook(a)lists.phcomp.co.uk> http://apc.io/library/ Rest of rant is here: http://pfalcon-oe.blogspot.com/2013/10/growing-gplfoss-loyalty-among-chines… -- Best regards, Paul mailto:pmiscml@gmail.com

4 3

3d on mali
by luke.leighton 06 Oct '13

06 Oct '13

joe just in case you don't see it: <focus_it> wingrime: i'm trying to get 3d working i follow advise here http://linux-sunxi.org/Binary_drivers and get these as my results http://www.gplsquared.com/eoma_boot/gles_errors1.txt <focus_it> any pointers helpful <lkcl> focus_it: ahh yeahhh... always a bit of a battle, that one <lkcl> focus_it: [ 19.657] (II) FBTURBO(0): can't load 'g2d_23' kernel module <lkcl> so you need to track down that kernel module (as a config option) and enable it <lkcl> also you need to put the mali driver in the correct place <lkcl> 20.524] (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/sunxi-mali_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/sunxi-mali_dri.so: cannot open shared object file: No such file or directory)

1 0

Re: [Arm-netbook] [flying squirrel] TODO list
by luke.leighton 04 Oct '13

04 Oct '13

well.... uh... it looks like i totally cocked up the ADC side of the flying squirrel circuit for the microphone! i must have been on drugs or something (someone slipped something into my hot water with a bit of milk). the connections i made to the LM13700 OTA bear absolutely no relation to the example schematics! luckily i did manage to connect +ve and -ve to the right pins, meaning that the 3 LM13700s i now have are absolutely fine, so i've spent the day putting resistors on one of them like a porcupine, experimenting. what's really awesome about the LM13700 is that it has a fascinating history of its own: http://www.idea2ic.com/LM13600/LM13700.html being an independent-buffered dual-version of an incredibly famous OTA - the CA3080 - which was first sold in *1969* http://www.till.com/blog/archives/2005/06/last_of_the_ota.html i'm reminded of when i put the flying squirrel schematics in front of a chinese ODM for them to quote helping get it made, they said "that's a really old school design". i had no idea :) anyway, i'm presently flipping quills on an LM13700 porcupine and also i'll errr... this time be actually... like... connecting the ADC VREF pins on the STM32F so that... y'know... the ADC actually works? honestly... :) l.

1 0

Re: [Arm-netbook] [flying squirrel] TODO list
by luke.leighton 02 Oct '13

02 Oct '13

On Thu, Sep 26, 2013 at 11:16 AM, luke.leighton <luke.leighton(a)gmail.com> wrote: > * find out why the AXP209 is randomly shutting off (could be floating reset?) *sigh* this turns out to be because (AGAIN) wits-tech did not... AGAIN ... tell us that they'd made changes which were NOT authorised, to the EOMA68-A20 CPU Card schematics. this time what they've done is wire the 5V (ACIN) directly to the USB-OTG line of the AXP209. *deep breath*.... the consequences of that are that when the device is being powered by USB-OTG, 5V appears on the EOMA68 5V power lines. the consequences of _that_ are that the flying squirrel I/O board (which has its own AXP209 and a 5V step-up regulator to turn IPSOUT into a stable 5.0V output) fights with the incoming 5V power... and loses the moment that the voltage fluctuates by even the smallest amount (such as the A20 doing anything resembling the slightest amount of processing). if wits-tech had fucking well told me what they were doing i could have put in a MOSFET or other power regulator on the I/O board to cope with power-in as well as power-out. not entirely sure what to do here, i'll have to think about it. as far as testing the flying squirrel is concerned i can get it working (in a rather painful laborious way) by disconnecting USB-OTG: i've verified that the CPU Card can in fact be powered by *incoming* 5V power from the I/O board... i might need to cut one of the micro-usb cables i have here and remove its 5V line or something. l.

3 11

[EOMA68] changes to I2C EEPROM address location
by luke.leighton 02 Oct '13

02 Oct '13

http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68#Requirements_f… i've updated the specification to reflect what's actually been deployed on the flying squirrel pcb. apologies but i'd read the AT24C64 datasheet incorrectly: the "1" in the 8-bit MSB of an I2C address is not counted in the address so i'd read it as "0xA2" when it should be "0x51". apologies but all boards currently being designed will need to update schematics to match accordingly. l.

3 3

Ubuntu 13.04 Desktop Linux now running on EOMA68-A20
by joem 01 Oct '13

01 Oct '13

Ubuntu 13.04 now running on EOMA68-A20 Sata disk images and how to's here: http://www.gplsquared.com/eoma_boot/eoma_boot.html#Ubuntu_13_04 (The same image can work on Cubieboard2 as well with some minor tweeks.) The EOMA now functions like a powerful arm-netbook desktop computer and as powerful as any netbooks that first came out. Probably under $50 BOM costs for a netbook like ARM PC box with say an upgradeable 16GB sata SSD built into the box. This release has Gambas3 compiled and working. Gambas allows rapid GUI application development. So - now very easy to customize EOMA to become IoT gadget with a GUI user interface, a web interface or both.

2 12

Re: [Arm-netbook] ARM system with good wifi
by luke.leighton 01 Oct '13

01 Oct '13

On Fri, Sep 20, 2013 at 4:04 PM, Stefan Monnier <monnier(a)iro.umontreal.ca> wrote: > The lack of other answers makes me suspect that all the builtin wifi > adapters on ARM systems just suck, IOW what I'm looking for > doesn't exist. there are two factors at play here. 1) the price-war on tablets is driving everything down. if you're putting in a high-quality $5 WIFI module you just made the entire product uncompetitive because everyone else is using $2 modules. when the product BOM is only $30 the higher-quality WIFI module represents a whopping 10% increase in the BOM. 2) low-end portable products need lower-power WIFI modules otherwise the battery has to be larger, and *again* that pushes up the price to uncompetitive levels. low-power WIFI modules tend to have shit-for-brains range the only other thing i can think of perhaps is for you to take some pictures of the wifi module, identify it, and then hunt around to see if there's a way for example to add an external antenna (or a better external antenna if it already has one). then make sure it's installed in a place that's away from any metallic objects inside the casework. the only problem with increasing the effectiveness of the antenna is that it can suck more power out of the module's R.F. transmitter (i don't fully understand this but it's what i've heard so i'm repeating it parrot-fashion). so you'll just have to watch out for that, ok? l.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

arm-netbook October 2013