<ssvb>
techn_: don't know, I did not pay much attention to it
bsdfox_ has quit [Ping timeout: 276 seconds]
tinti has quit [Quit: Leaving]
hp__ has quit [Ping timeout: 264 seconds]
Turl has quit [Quit: >.<]
specing has quit [Ping timeout: 246 seconds]
stefanro has joined #arm-netbook
specing has joined #arm-netbook
stefanro1 has quit [Ping timeout: 255 seconds]
alcides has joined #arm-netbook
alcides has quit [Changing host]
alcides has joined #arm-netbook
alcides has quit [Quit: > SELECT * FROM users WHERE clue > 0]
jlj has quit [Remote host closed the connection]
cnxsoft has joined #arm-netbook
penguin42 has quit [Quit: Leaving.]
<drachensun>
my wifi has stopped working on some devices and I notice that the devices that don't work have a bunch of echi reset messages when the 8192cu driver is loaded and unloaded
<drachensun>
has anyone else seen that?
<vinifm>
try use rtlwifi
fragmint has quit [Read error: Connection reset by peer]
<lkcl>
ln22: i've had to take a full-time job, so when i get home i carry on working for another 5 hours on PCB CAD/CAM. apologies but it leaves little spare time for talking to people. i'm doing status reports.
<lkcl>
the tablet PCB will fit into a laptop as well (low-power, single LVDS up to about an 11in screen, 1388 x 800 or so)
<lkcl>
that's now with the engineers
<lkcl>
the A10 board, the 2nd revision has started
<lkcl>
and the iMX6 board is still at a very early stage, i started it a few weeks ago and have been learning the CAD/CAM software on-the-go.
<ln22>
This is great thank you!
<ln22>
lkcl: Is there an EOMA-68 board planned with dual LVDS?
ganbold_ has joined #arm-netbook
rz2k has quit []
<lkcl>
ln22: EOMA-68 doesn't do LVDS, it does 24-pin RGB/TTL. so you do the conversion - to absolutely anything - on the I/O board.
<lkcl>
at some later date, the flying squirrel board will be converted to dual LVDS output. however as dual LVDS screens typically need more power, that has knock-on ramifications for the power management, so that's pretty much a redesign, right there.
<lkcl>
what i'm hoping to be able to do is use bunny's iMX6 laptop schematics, and just integrate the circuits he used for battery charging and power management
<lkcl>
i'll have to double-check with him that the parts are mass-volume and available in china
<lkcl>
because as you saw from the rbpi, they picked a XTAL that was only available in europe, and had to do a board-level redesign. that's baaaad :)
<lkcl>
actually, you need them. each layer *needs* to stand out from all other layers. that means using eye-burning colours. which i find quite attractive, but i also like sparkly-sparkly pavements (the ones with bits of flint in them)
<lkcl>
that should tell you everything you need to know :)
eebrah is now known as eebrah|away
* jelly-home
bets lkcl also likes ponies in bright colors
doneill has joined #arm-netbook
<doneill>
Hey guys, is a firmware necessary for a Realtek 8192CU to be detected? My module loads fine, but dmesg doesn't pick up the device. The netbook is an E6 (Allwinner A10) and I'm using the git master branch kernel from linux-sunxi.org, 3.0.62 at the moment. On the Android kernel it ships with (3.0.8) the chipset loads fine, but the output looks very different.
vinifm has joined #arm-netbook
<vinifm>
hi, what is the difference between ump and mali drivers
<Turl>
doneill: what kernel module are you using for it?
Quarx has quit []
<Turl>
doneill: make sure you enable the usb controller on script.bin if using mainline's rtlwifi one
<doneill>
8192cu
Quarx has joined #arm-netbook
<doneill>
The Android installation also loads 8188 and some others, but I think it's because the firmware is shared with other boards using different chipsets.
<drachensun>
doneill: what does lsusb say is the model
<drachensun>
yeah, I spent last night fixing that for my PengPods
<doneill>
drachensun, that was my next bet, but dmesg pretty clearly uses 8192cu for the device, unless 8188eu depends on 8192cu
<drachensun>
doneill: it doesnt
<doneill>
All 3 USB controllers are enabled, and usb_wifi_used is 1, I guess I'll pull the script.bin from the nand and compare the fex.
<doneill>
Maybe it's GPIO after all, though I've never seen that. Would be slow as hell I'd think.
<doneill>
Are I2C or SPI wifi chips common on sunxi boards?
eebrah|away is now known as eebrah
<drachensun>
I haven't seen one and I own a pretty good collection here
<drachensun>
is this a netbook by any chance?
<doneill>
Yep it is.
<drachensun>
yeah duh, you said netbook
<drachensun>
it has 3 usb ports right?
<doneill>
hehe I have a good collection coming along too now
<doneill>
Yep on one side
<drachensun>
so probably they had to give up the one they use for wifi in the other devices
<jelly-home>
where can one buy such a A10-powered netbook?
<doneill>
Well I haven't poked around too much, I figured I'd ask before stumbling through in the off chance somebody has sorted this out.
<drachensun>
I have a couple of those here too but I managed to fry one trying to solder a debug header on and never got around to working with the other
<doneill>
jelly, I got several cases of various ARM netbooks and tablets from a supplier in Shenzhen on Alibaba.com
Quarx has quit [Remote host closed the connection]
<doneill>
wm8850 is interesting but the hardware around it is pretty challenging to support.
<doneill>
I got some q88 tablets which rock but the touchscreen driver basically doesn't exist in source form, from what I've found. ZET6221 is the chipset. I've been hacking up a driver over the last week but it doesn't even compile yet.
<drachensun>
Allwinner def. has the most advanced community source of any of those Chinese devices
eebrah has quit [Ping timeout: 276 seconds]
eebrah has joined #arm-netbook
<libv>
we are also quite unique in that hipboi provided us with mali builds that somewhat work
<libv>
try finding mali builds for non-android systems on other SoCs
<jelly-home>
is A10 inability to deal with a sata port multiplier a hardware or a software issue or both?
ln2 has joined #arm-netbook
ln2 has quit [Client Quit]
gzamboni has joined #arm-netbook
rsalveti has quit [Read error: Connection reset by peer]
rsalveti has joined #arm-netbook
rsalveti has quit [Quit: Bye]
rsalveti has joined #arm-netbook
discopig has quit [Read error: Connection reset by peer]
merbzt has quit [Ping timeout: 252 seconds]
discopig has joined #arm-netbook
GeorgeIoak has joined #arm-netbook
<hramrach>
jelly-home: it's in the hw datasheet afaik
<hramrach>
so not designed to do that
datagutt has quit [Quit: kthxbai]
<hramrach>
lkcl: is it difficult to find chip for converting RGB to DP/eDP?
<hramrach>
there was some discussion about new panels being cheaper but eDP which required expensive conversion chip to go LVDS->eDP
<hramrach>
also is it even possible to build an eoma card around something moderately powerful like Exynos?
<hramrach>
the ODROID comes whit quite large heatsink which you can't stuff into a PCMCIA card
<ln22>
Yeah. I am also extremely interested in eDP panels on the AMD SoC EOMA-68 card. The chip fully supports eDP.
<hramrach>
I guess the AMD chips would have the same heat problems as Exynos
<hramrach>
in addition to being lame hardware
doneill has quit [Ping timeout: 245 seconds]
<ln22>
It's easy to call them lame. But the AMD chips will have 3d acceleration and opencl. Two things we don't have on other ARM devices running Linux.
vinifm has quit [Quit: Ex-Chat]
<hramrach>
and they will randomly lock up when you upload random assembly to them
<hramrach>
whereas Mali reportedly processes any assembly without lockups
discopig has quit [Remote host closed the connection]
<ln22>
The AMD SoC's have that behavior? You have been developing on them?
discopig has joined #arm-netbook
<hramrach>
ln22: AMD cards have that behvoiur. If you look the SoC datashets they list the desktop AMD cards that do that
<hramrach>
of course, they could fix them for the SoC
<hramrach>
but they could fix the dozens of desktop cards, and didnt
<L84Supper>
an AMD EOMA card is doubtful, it could be a BEOMA card though, no real problems with thermal management with AMD, what problem does Exynos have?
<L84Supper>
hramrach: ^^
gimli has joined #arm-netbook
tinti has joined #arm-netbook
<hramrach>
L84Supper: compared to A10 it needs way more cooling
<hramrach>
but if T40 works Exynos will possibly work too
<L84Supper>
EOMA has no thermal spec since they don't understand thermal management
<hramrach>
;-)
<L84Supper>
but it could support either
<hramrach>
what is beoma?
<L84Supper>
better eoma :)
tinti has quit [Quit: Leaving]
<L84Supper>
or maybe weoma for working eoma
<hramrach>
why A10 is not working?
<L84Supper>
a10 works just not eoma
<hramrach>
they are designing it ;-)
eebrah is now known as eebrah|away
rellla has quit [Quit: rellla]
<L84Supper>
13 months +
<hramrach>
first project
<hramrach>
difficulties :p
<hramrach>
is there not better widely available connector btw?
eFfeM has quit [Quit: Leaving.]
<hramrach>
turns out the cpmcia has way few pins for the amount of outputs chips usually have
eebrah|away has quit [Quit: ChatZilla 0.9.90 [Firefox 18.0.2/20130201065344]]
<hramrach>
I guess it can't be something ultra miniature when used for power as well so something like hotplug ata/scsi coneectors comes to mind
<L84Supper>
there are some higher pin count high durability connectors
<hramrach>
but those are dying out for sata/sas
<L84Supper>
you only need them for applications where you're going to swap cards around
<L84Supper>
most apps will only stay in place of only get swapped a few times
<L84Supper>
of/or
<L84Supper>
for high durability you need self lubricating contact >1k cycles
<hramrach>
but you cannot tell which application you have until the users start whining that the connector does not last
wingrime has quit [Ping timeout: 245 seconds]
<hramrach>
the internal SATA is designed for something like 100 cycles iirc