arm-netbook

arm-netbook@lists.phcomp.co.uk

8 participants
1076 discussions

Re: [Arm-netbook] Home microserver based on ARM
by mike.valk＠gmail.com 30 Sep '13

30 Sep '13

2013/9/27 Stefan Monnier <monnier(a)iro.umontreal.ca> > >> But to use something like the quattro docking station, either you have > >> to use a USB connection (rather undesirable, especially since all those > >> ARM thingies seem to be limited to USB-2.0 so far), or you have to use > >> a SATA connection where the controller supports "port multiplier". > > Both types support sata multiplier. > > I lost you: both types of what? Both the i.MX6 and the A10/A20 SoCs? > You lost me twice. There Are two CuBox modules now: 1st CuBox/CuBox Pro. Which Has the Marvell Armada. http://www.solid-run.com/mw/index.php?title=CuBox_hardware_specification 2nd CuBox-I. Which comes in the four flavors of i-MX. http://imx.solid-run.com/wiki/index.php?title=CuBox-i_Hardware Unfortunately they don't have a Allwinner A10/A20 version. There HW design is quite good and sw hacker frendly. Eg. built-in USB->UART chip. > > > Just read that the original CuBox does it better. The Marvell armada one. > > That is. > > It seems that the Inc doesn't support asynchronous transfer. > > Are you saying that the Armada chip only supports the "command based > switching" (so only one drive can be active at a time), whereas the > i.MX6 (used in CuBox) supports "FIS–based switching" (commands can be > sent to drives regardless if other drives still haven't finished > processing previous commands)? > Just the opposite: 1st: Marvell Armada -> FIS Based switching 2nd: i-MX -> Command based switching http://www.solid-run.com/phpbb/viewtopic.php?p=8001&sid=c661b1aaed86bc1a510… (posted by Rabeeh; The company's founder/CTO) > > > Stefan > > > _______________________________________________ > arm-netbook mailing list arm-netbook(a)lists.phcomp.co.uk > http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook > Send large attachments to arm-netbook(a)files.phcomp.co.uk >

2 1

Re: [Arm-netbook] ARM system with good wifi
by mike.valk＠gmail.com 30 Sep '13

30 Sep '13

2013/9/19 Stefan Monnier <monnier(a)iro.umontreal.ca> > I'd like to use something like a Mele-A2000 (i.e. one of those > cheapish-but-beefier-than-linksys-router ARM systems) as access point, > but my Mele-A2000 has a pretty weak wifi. Part of the problem is the > wifi driver I suspect, but other things like the antenna are probably > not helping. > > Does anyone have a product to recommend, based on something comparable > to an Allwinner SoC, but where the wifi is of good quality? > Dunno if it actually works, but A20/A10 with an external antenna: https://www.miniand.com/products/Mini%C2%A0Xplus%20TV%20Box%20H34 https://www.miniand.com/products/Mini%C2%A0Xplus%20TV%20Box%20H24 > > > Stefan > > > _______________________________________________ > arm-netbook mailing list arm-netbook(a)lists.phcomp.co.uk > http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook > Send large attachments to arm-netbook(a)files.phcomp.co.uk >

2 1

Re: [Arm-netbook] AC to DC power adapter with multiple outputs
by Benson Mitchell 30 Sep '13

30 Sep '13

On Sep 29, 2013 9:50 AM, "Dr. David Alan Gilbert" <dave(a)treblig.org> wrote: > Have you tried a normal PC power supply; I think there is a way to fudge > them to believe a motherboard is connected. That's the ticket. But there is one gotcha with this -- some PSUs won't operate or don't operate well with no or very low load (they need like 1-5% of rated current, minimum). So check the voltages with no load, if all seems well, good! otherwise, throw a 12V light bulb on the output and that should make it behave. Benson

3 2

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

29 Sep '13

argargargh, the USB is connected the wrong way round to the STM32F. arghargargh :) so i have to carefully pull up 2 legs of the STM32F then solder flying leads underneath them.... *gibber*

1 0

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

29 Sep '13

root@debian:~# i2cdetect 1 WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-1. I will probe address range 0x03-0x77. Continue? [Y/n] y 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- 15 -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- 34 -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- woo! 0x51 i think is the eeprom, 0x15 the 3d sensor, 0x34 the AXP209. let's plug in the touch panel.... i2cdetect 1 WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-1. I will probe address range 0x03-0x77. Continue? [Y/n] y 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- 15 -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- 34 -- -- -- 38 -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- haaaaaa :)

1 0

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

28 Sep '13

woo! root@debian:~# lsusb Bus 002 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 003: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter

2 7

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

arm-netbook