mnemoc changed the topic of #arm-netbook to: EOMA: Embedded Open Modular Architecture - Don't ask to ask. Just ask! - http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68 - ML arm-netbook@lists.phcomp.co.uk - Logs http://ibot.rikers.org/%23arm-netbook or http://irclog.whitequark.org/arm-netbook/ - http://rhombus-tech.net/
hg_5 has quit [Ping timeout: 256 seconds]
captainigloo has quit [Ping timeout: 245 seconds]
captainigloo has joined #arm-netbook
gimli has quit [Ping timeout: 246 seconds]
hp__ has joined #arm-netbook
popolon has quit [Quit: Quitte]
stefanro has joined #arm-netbook
stefanro1 has quit [Ping timeout: 245 seconds]
hp__ has quit [Ping timeout: 276 seconds]
captainigloo has quit [Ping timeout: 246 seconds]
captainigloo has joined #arm-netbook
hp__ has joined #arm-netbook
RITRedbeard has joined #arm-netbook
captainigloo has quit [Ping timeout: 244 seconds]
captainigloo has joined #arm-netbook
alcides has quit [Quit: To be continue...]
mSquare has joined #arm-netbook
SouL_ has joined #arm-netbook
SouL_ has left #arm-netbook [#arm-netbook]
ZaEarl has quit [Ping timeout: 252 seconds]
rz2k has joined #arm-netbook
atari2600a has joined #arm-netbook
<atari2600a> hey
<atari2600a> I've heard the new chromebook has a DIMM slot on it but I'm also hearing the memory's onboard
<atari2600a> can someone clear that up?
<xenoxaos> which chromebook
<xenoxaos> the arm one....hell no
<xenoxaos> it's all soldered on
<atari2600a> but the samsung website's technical specs says there's a DIMM slot...
<xenoxaos> ?
<xenoxaos> link?
<atari2600a> well look at fucking that
<atari2600a> they fixed it
<atari2600a> my hopes & dreams are all shattered
<atari2600a> so, what's this channel for?
<xenoxaos> 2G is plenty for arm
<atari2600a> xenoxaos, 2G is bare-minimum for Ubuntu w/ Unity
<xenoxaos> i sit around 150M
<xenoxaos> exactly
<xenoxaos> fuck ubuntu
* xenoxaos loves arch
<atari2600a> oh, right, arch
<xenoxaos> just pushed a rootfs yesterday
<atari2600a> I'd be more interested in sudo apt-get installing xubuntu-desktop than installing arch though
<atari2600a> though, for shits & giggles I installed gentoo on a 1GB netbook years ago
<atari2600a> so, how are YOU guys dealing w/ the death of the netbook?
<xenoxaos> i'm probably going to also release a image with x already set up
<atari2600a> (& remergance of the concept through the chromebook)
<xenoxaos> i've had ultraportables for years
<xenoxaos> bought a hp with a 1024x600 screen..
<xenoxaos> said fuck that and got a differnt one with 1366x768
<xenoxaos> 11" is the best size imo
<atari2600a> I prefer 9"
<atari2600a> I loved my eeePC 900A
rmull has quit [Ping timeout: 260 seconds]
<atari2600a> it would fit in my pocket, hold it on one hand & type w/ another
rmull has joined #arm-netbook
<atari2600a> & once you pulled all the keys off & re-arranged into Dvorak it was total computer mindcum everywhere
<xenoxaos> thats what the fujitsu lifebooks were for
<atari2600a> oh, I had a Fugitsu Livebook 735dx when I was 9
<atari2600a> it's the laptop that taught me (through failure, the best kind of learning!) I needed to ORGANIZE my screws when doing a pointless teardown
<xenoxaos> lol
<atari2600a> well, BRB
<atari2600a> I'm gonna go watch a movie over skype w/ my girlfriend
<atari2600a> (we both download the same film & manually stay in sync w/ eachother
<xenoxaos> enjoy\
Gujs has quit [Ping timeout: 260 seconds]
Gujs has joined #arm-netbook
Guest52002 has quit [Ping timeout: 245 seconds]
Guest52002 has joined #arm-netbook
HACKhalo2 has joined #arm-netbook
Quarx has joined #arm-netbook
Curtman has quit [Quit: Leaving]
rsalveti_ has joined #arm-netbook
rsalveti has quit [Ping timeout: 244 seconds]
rsalveti_ is now known as rsalveti
jquip has joined #arm-netbook
jquip has quit [Quit: jquip]
jquip has joined #arm-netbook
_hp_ has joined #arm-netbook
<hno> slapin, CMD_TYPE_1 seems to be ECC fetch.
cat_x301 has quit [Ping timeout: 240 seconds]
jquip has quit [Ping timeout: 260 seconds]
RITRedbeard has quit [Read error: Connection reset by peer]
RITRedbeard has joined #arm-netbook
RITRedbeard has quit [Read error: Connection reset by peer]
rellla2 has joined #arm-netbook
rellla has quit [Ping timeout: 252 seconds]
cat_x301 has joined #arm-netbook
RITRedbeard has joined #arm-netbook
jquip has joined #arm-netbook
HACKhalo2 has quit [Ping timeout: 246 seconds]
<hno> slapin, it always fetches the ECC size amount of data, and no trace of the data anywhere except that maybe user_data[0] gets updated.
<hno> Need to find a page with some ECC errors to test if it also does ECC processing.
<hno> but I hope it does.
ssspiff has joined #arm-netbook
sspiff has quit [Ping timeout: 255 seconds]
jquip has quit [Ping timeout: 246 seconds]
<rz2k> interesting, glmemperf shows 11fps on x11 mali libs
<rz2k> and crashes on one of the tests.
<oliv3r> so anybody excited about the POSSIBLE powerVR drop?
cheng has joined #arm-netbook
<rz2k> you seriously wait something from imagination tec.?
<sv> what about powevr
<oliv3r> you guys don't read phoronix?
<oliv3r> appearantly there may be some oss support or a source drop coming from powerVR during the holidays
<oliv3r> including 3D userspace
<oliv3r> but nothing set in stone yet of course
cheng has quit [Quit: Leaving]
gimli has joined #arm-netbook
<hno> oliv3r, not holding my breath waiting for something useful to fall out there. But who knows what it means.
* slapin does have 2 pandaboards, it might benefit them
<sv> that sounds pretty awesome ol1ver1
<oliv3r> well we won't know till the holidays
<oliv3r> and we probably get nothing usefull, but hey, who knows
ol1ver1 has quit [Quit: ol1ver1]
<mnemoc> the bigger the hopes, the bigger the disappointment
<oliv3r> i'm trying to get all your hopes down!
cat_x3011 has joined #arm-netbook
<libv> oliv3r: not me, there were rumours before that intel was going to do an open source driver, but that never materialized
<oliv3r> the G500 you mean?
<oliv3r> the 'poulsbo'?
<libv> plus, i doubt imagination is doing all the work necessary
<libv> and i would really really recommend people to sink their time into sane designs which can actually fly in the current highly competitive market
cat_x301 has quit [Ping timeout: 248 seconds]
<libv> and let imagination do the work of cleaning up their heap of... themselves
<libv> mali, adreno, tegra, vivante, all are sane gpus
The-Compiler has quit [Quit: WeeChat 0.4.0-dev]
The-Compiler has joined #arm-netbook
cat_x3011 has quit [Ping timeout: 260 seconds]
jquip has joined #arm-netbook
tzafrir_laptop has joined #arm-netbook
popolon has joined #arm-netbook
<slapin> libv: what is so wrong about powervr, comparing to e.g. mali?
<libv> slapin: hw <-> huge bit of microcode <-> kernel <-> userspace
<libv> all are highly interdependent and have no clean or clear interfaces
<slapin> libv: where does microcode executes? on CPU?
<libv> heh
<libv> where is microcode usually executed?
<slapin> libv: that depends on how you use the term
<libv> in this case, on one of the pvrs processors
<libv> it is highly pvr hw revision dependant
<libv> then, the microcode and the kernel share structs, there is an abi between them which is highly fragile
<slapin> libv: and every SoC contains their own hw revision?
<slapin> awwwww
* slapin hates that since that dlink wicked router
<libv> then the interface to userspace is such that you never ever know what the f is going on
<libv> because they go for max confusion there
<libv> so whatever userspace they are going to make available, if at all, it's going to be pretty pointless
<slapin> so all design goal is to make it as hard to understand as possible?
<libv> the whole thing is way too fragile and too dense
<libv> i don't know, i still do not understand the reasoning behind this mess
<slapin> libv: too many developers per line of code?
<libv> i just know that time is better spent cleaning up sunxi or other crap chinese vendors soc code
<libv> i rank that as way more useful than pvr, so go figure
svp has joined #arm-netbook
<jquip> yay! i got logs coming from usb to ttl :D Thanks a lot hno, slapin, libv, oliv3r !
<libv> jquip: cool, congrats
<oliv3r> jquip: what did you change to make it happen?
<jquip> hahah I wouldn't even have figured out the pin configuration is it weren't for you guys!
<libv> jquip: now you can go hack uboot into submission, there is code on the ml for getting the dram timing needed for uboot
<libv> jquip: thank hno for that one
<jquip> hno : THANKS for the pin config :D
<jquip> oliv3r: so here's my pin config
<libv> jquip: make a wiki page for your tablet
<libv> jquip: add pictures of the board, and how to wire up serial
<jquip> A10 Board | USB-ttl-Chip
<jquip> Pin1[square] | Rx
<jquip> Pin2 | Tx
<jquip> Pin3 | --
<jquip> Pin4 | GND
<jquip> Pin5 | GND
<jquip> YES will do that..
<oliv3r> ping3 isn't VCC?
<jquip> It is ...
<jquip> but you dont need to connect it, because ttl device has power, and a10 device has power...
<jquip> so need to... libv said that earlier yesterday
<jquip> s/need/no need/
<ibot> jquip meant: so no need to... libv said that earlier yesterday
<jquip> pin3 is 3.3V
<oliv3r> jquip: it is ttrue, just wondering IF the A10 outputs VCC on pin3 at all :) and i guess you only need one of those GND pins ;)
<jquip> minicom -b 115200 -D /dev/ttyUSB0 -L -C u-boot_ttl.log
<jquip> this also helps :)
<jquip> yes it does. checked with multimeter
<jquip> yes we can do with one of the GND pins, I haven't tested to be sure.. but should work
<jquip> "Pin3 is 3.3 V" -Multimeter
<jquip> libv: Any link for how to hack uboot ??
<libv> jquip: when you follow first steps howto, two things will be missing
<libv> jquip: the .fex for your device, and the board specific uboot
<libv> jquip: you can look at the uboot commits to see how to add device specific uboot, and, as i said earlier, there is a tool on the ml for the dram info
jquip has quit [Ping timeout: 264 seconds]
RITRedbeard_ has joined #arm-netbook
RITRedbeard has quit [Read error: Connection reset by peer]
madmalkav has joined #arm-netbook
wim has quit [Ping timeout: 264 seconds]
wim has joined #arm-netbook
rz2k has quit []
hg_5 has joined #arm-netbook
hg_5 has quit [Ping timeout: 252 seconds]
jquip has joined #arm-netbook
<hno> jquip, the VCC is only needed if you have an UART that takes a reference voltage input. Should be left unconnected with most UARTs.
<jquip> hello hno :) oh so on most boards we will never need to connect the VCC of the ttl..
<hno> jquip, it's a matter of what UART dongle you have, not the board. Fixed 3.3v dongles MUST NOT have VCC connected.
<jquip> ahhh i see..
<hno> which covers practically all basic UART dongles you find on the market.
The-Compiler has quit [Quit: WeeChat 0.4.0-dev]
The-Compiler has joined #arm-netbook
<jquip> mine has a 5V and 3.3V pin as well...
<jquip> that makes it an exception?
<hno> There is some more advanced dongles that can operate at a wide range of voltage ranges and those wants a reference voltage input indicating the target board voltage.
<hno> Usually labelled Vio or Vref.
<jquip> * nods... * need to read more to match hno's insane level of knowledge
<jquip> So here is the scene: I'm trying to get linux onto the flash...
<jquip> which Filesystem is possible now?
<jquip> which filesystem is best?
<jquip> I hear ext4 is possible right now... drivers for that exist..
arokux has joined #arm-netbook
<jquip> but the thing with ext4 is that multiple writes to the NAND will wear it out quickly..
<jquip> can we do another filesystem as of now??
<jquip> yaffs2 perhaps?
<jquip> if I remember properly the default android kernel log shows that yaffs2 filesystem was loaded ..
<jquip> so we might have support for it since we have forked from the lichee kernel sources already right?
<mnemoc> jquip: not until we have an mtd driver
<mnemoc> and hno and slapin are having a bad time trying to deal with the nfc directly
<jquip> slapin and hno were working on mtd I think? some ML thread
<mnemoc> yes, working on it
<mnemoc> but not ready for use
<mnemoc> only "understanding" it
<mnemoc> as there is no documentation beside the current drivers
cat_x301 has joined #arm-netbook
<jquip> I still just want to see it booting from the memory.. I might as well get it running using the ext4 for now.. just want it to boot it faster and more reliably... the SD card boot is very erratic...
<hno> mnemoc, not really bad. Just many unknowns
<slapin> we can really read pages, but full page read is still fails
<mnemoc> jquip: you can boot from nand today using u-boot-sunxi's lichee-dev branch
<jquip> really? :D
<jquip> I'm going to give it a shot...
<mnemoc> jquip: it's intended as a drop-in replacement to nanda's linux/u-boot.bin
<jquip> no params to be changed?
<mnemoc> only if you want it
<mnemoc> but it's fully open and well behaved (passing proper ATAG info)
<mnemoc> doesn't match the goal of mainling, but helps people who wants a mostly-free boot chain on nand
antonl has joined #arm-netbook
<jquip> mnemoc: that's really nice :) I'm cloning ... I think you meant lichee/ branch, there is no lichee-dev/ branch
<mnemoc> there is
<mnemoc> lichee/* are historic
<hno> hi slapin
<jquip> oh sorry yes i see it... I was reading the wiki page..
<mnemoc> hno: slapin: maybe what you see as "page size" is a "real page size + metadata" and that's why you can read the whole?
<mnemoc> masking something our or similar
<mnemoc> out*
SouL_ has joined #arm-netbook
SouL_ has left #arm-netbook [#arm-netbook]
wim has quit [Ping timeout: 264 seconds]
wim has joined #arm-netbook
alcides has joined #arm-netbook
alcides has quit [Changing host]
alcides has joined #arm-netbook
<hno> I don't know whats wrong with the oob part. Seems to be read correctly from the nand.
<hno> but really need hardware randomizer & ecc enabled to make sense of nand contents.
<hno> arg, one cable loose on my olimex jtag hack. soldering time again.
<hno> would like to spy a little on BROM NAND operations. Seems I am missing some small detail in how it reads boot0.
<hno> Info : JTAG tap: sun4i.dap tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4) B-)
svp has left #arm-netbook [#arm-netbook]
<hno> and now encapsulated in glue so the cables should stay in shape.
<xenoxaos> hot glue guns are a necessity for all hackers!
<jquip> :D hno iz keepin it cool!
Ershov has quit [Quit: Ershov]
<hno> hot glue is seriously underestimated.
<hno> And NAND controller trace of BROM loading boot0 collected.
<hno> Hm... probably should have traced DMA operations as well, or at least amount of data transferred using DMA.
<oliv3r> so success? :D
RITRedbeard_ has quit [Read error: Connection reset by peer]
rz2k has joined #arm-netbook
cheng has joined #arm-netbook
<hno> oliv3r, progress.
<oliv3r> potatoes tomatoes
<slapin> hno: hi!
<slapin> hno: any news?
antonl has quit [Ping timeout: 260 seconds]
specing has joined #arm-netbook
itamar_ has joined #arm-netbook
<slapin> too much cola in my head :(
ibrah has joined #arm-netbook
Mazon has quit [Quit: meh]
SouL_ has joined #arm-netbook
<oliv3r> hmm, there's something I don't understand. I see in the docs, that there's some SRAM's, one of which, SRAM C1, C2, C3. Also there's a dedicated SRAM for USB usage. Yet I see SRAMC used all over USB bits in sun4i header files
<oliv3r> the thing is, I also see wemac using SRAM C a lot
<oliv3r> won't that conflict at all?
SouL_ has left #arm-netbook [#arm-netbook]
<oliv3r> also, is it good practise to redefine these memory ranges through several header files? Isn't that supposed to be more central somewhere in march?
jquip has quit [Quit: jquip]
<hno> Aha. boot0 have different ECC layout and random seed than normal NAND access.
<hno> slapin, yes. But nothing conclusive yet.
<oliv3r> progress! :p
<hno> Did manage to read the MBR in descrambled form by fiddling with registers. Not sure if it did ECC processing.
<hno> SEQ bit changes the ECC layout to sequencial. <data> <ecc> <data> <ecc> .... instead of the more normal <data> <data> <data> ... <ecc> <ecc> <ecc> ...
<hno> now trying to read & descramble the boot block, but only get random data.
<hno> slapin^
<oliv3r> do we know if that could possibly be encrypted? or do we know what should/could be on the boot block?
<hno> It's not encrypted. Only randomized.
<hno> content is known, just not fully known how to get that content in readable form without using DMA.
<hno> or how to make use of the ECC function without using DMA.
<hno> All reference code we have uses DMA.
<oliv3r> :(
<hno> Even including BROM.
<oliv3r> :S
<oliv3r> there, SRAM registry mapping added to the wiki :)
<oliv3r> homeitme :)
hg_5 has joined #arm-netbook
SouL_ has joined #arm-netbook
SouL_ has left #arm-netbook [#arm-netbook]
revident has joined #arm-netbook
madmalkav has quit [Quit: Leaving]
Guest52002 has quit [Quit: Ciao guys]
madmalkav has joined #arm-netbook
<slapin> hno: we need to know the cpu ECC layout too, to make bootable NAND.
<slapin> hno: how did you manage to read partition table?
lufu has joined #arm-netbook
rz2k has quit []
mSquare has quit [Ping timeout: 240 seconds]
cheng has quit [Quit: Leaving]
<hno> slapin, bu replaying the address & random set by NAND u-boot.
lufu has quit [Remote host closed the connection]
<hno> slapin, it's pretty obvious how to read/write ECC+RANDOM data using DMA.
<hno> but not obvious how to do the same without DMA or by using the CPU for ECC+RANDOM.
<mnemoc> so just use DMA :p
cat_x301 has quit [Ping timeout: 264 seconds]
<hno> page oriented commands do all the magic automatically, but seems that command type only work using DMA.
Mazon has joined #arm-netbook
<hno> mnemoc, will quite likely end up there.
<hno> command type 1 is obviously ECC access, but still some doubts on how that really works.
drachensun has quit [Quit: Leaving]
<slapin> hno: probably other bit settings make sence?
<hno> slapin, what?
<slapin> hno: e.g. RAM_METHOD
<hno> That switches who sees the SRAM. But have no effect on page commands. After a page command SRAM is always locked out from the CPU, and NAND controller waiting for DMA. Have to reset it to return to useful state, which also reveals the expected content in SRAM.
<slapin> hno: have you tried to read IO_DATA with md.b/md.l after that?
RITRedbeard has joined #arm-netbook
rellla2 has quit [Ping timeout: 255 seconds]
vgrade_ has quit [Quit: Page closed]
<techn> hno: I tried those higher voltages for a10 tablet.. was no help
<techn> with newer kernel it crashes in different place.. but reason is same.. Unable to handle kernel paging request at virtual address bf00079c
<techn> and dram params are same as what a10-meminfo gives
ZaEarl has joined #arm-netbook
<hno> slapin, yes, it returns nothing. Or to be exact value of last other register read.
popolon has quit [Quit: Quitte]
tinti has joined #arm-netbook
itamar_ has quit [Remote host closed the connection]
<hno> techn, do you have the right scrip.bin?
<techn> hno: yes
revident has quit [Quit: Combustible lemons? Bah, I bring you weaponized asparagus!]
<techn> dram params are as with a10-meminfo
RITRedbeard has quit [Ping timeout: 245 seconds]
Quarx has quit []
SouL_ has joined #arm-netbook
SouL_ has left #arm-netbook [#arm-netbook]
HACKhalo2 has joined #arm-netbook
tinti has quit [Remote host closed the connection]
ibrah has quit [Ping timeout: 260 seconds]
tinti has joined #arm-netbook
hp__ has quit [Read error: Connection reset by peer]
<techn> hno: http://dl.linux-sunxi.org/AXP/AXP202%20Datasheet_v1.0_en.pdf, register 12h.. I'm wondering why you didn't enable those bits?
orly_owl has quit [Ping timeout: 255 seconds]
ibrah has joined #arm-netbook
drachensun has joined #arm-netbook
hg_5 has quit [Ping timeout: 248 seconds]
orly_owl has joined #arm-netbook
vgrade has quit [Quit: Lost terminal]
<techn> setting those didn't help eighter
<techn> lol
<techn> I tried with SD card from Mini-x and it didn't crash
madmalkav has quit [Read error: Connection reset by peer]
hp_ has joined #arm-netbook
<techn> [ 15.570000] sw_ahci sw_ahci.0: AHCI is disable
<techn> <4>sw_ahci: probe of sw_ahci.0 failed with error -22
vgrade has joined #arm-netbook
<techn> that could be the actual reason.. which corrupts memory :/
ibrah_ has joined #arm-netbook
ibrah has quit [Ping timeout: 260 seconds]
ibrah_ is now known as ibrah
_hp_ has quit [Ping timeout: 246 seconds]
hp__ has joined #arm-netbook
RITRedbeard has joined #arm-netbook
ibrah has quit [Ping timeout: 264 seconds]
Jef91 has joined #arm-netbook
<Jef91> Any suggestions for getting Ubuntu/Debian booting on the MK802? all the .img files I've tried just leave me with a blank screen
<drachensun> you probably need the script.bin from Android for the image
<Jef91> script.bin drachensun?
<drachensun> its the settings for your device
<drachensun> you'll need to get a copy from the Android image and use to replace whatever script.bin came with the image you downloaded
<Jef91> where does script.bin go in the image?
Mehhh has quit [Quit: Page closed]
<drachensun> the boot partition, if you insert the sd card in your PC you should see too partitions
<Jef91> Yea - so the vfat one with uboot
<drachensun> thats it
<Jef91> uImage*
<Jef91> This image has a "evb.bin" and "uImage" in the vfat partition by default
<drachensun> should already be a script.bin file in there
<Jef91> could evb.bin be the script.bin drachensun?
<drachensun> ok, evb.bin is the same thing
<drachensun> so when you pull from your device, rename it to script.bin
<drachensun> its also possible your device uses evb.bin
merbzt has joined #arm-netbook
<Jef91> drachensun: Please forgive my ignorance - what does "adb access" mean? How do I get that?
<drachensun> Android debug bridge, http://developer.android.com/tools/help/adb.html
<techn> hno: ok.. solved.. atleast partially.. solution was to change "sata_used = 0" to "sata_used = 1"
<drachensun> basically you need the android sdk
<libv> Jef91: i think you should be able to get away with running through our first steps guide
<Jef91> link libv?
<libv> Jef91: this means building filesystems, uboot and the kernel from scratch, and using a rootfs of your choice
<Jef91> Urg that is a ton of work for something that may end up getting me nil.
<libv> Jef91: i believe that we support the mk802 quite well at this point
<Jef91> there are images posted on miniand.com none of which worked for me
<Jef91> (side note are you the same libv that posted on my blog? http://jeffhoogland.blogspot.com/2012/11/raspberry-pi-vs-mk802.html )
<libv> Jef91: 512 or 1GB ram?
<libv> Jef91: yes
<Jef91> 1gig of RAM libv
<libv> so it is the mk802ii if i am not mistaking
<Jef91> I *think* this is just a plus
<libv> mnemoc? ^
<mnemoc> the ii has more USBs and stuff
<libv> ah, i see
<mnemoc> the + and the ii both have 1GB
<mnemoc> also both have AXP209
<libv> so we would need a dram config dump?
<libv> or should Jef91 just use the mk802ii config?
<mnemoc> in the worst case, https://github.com/maxnet/a10-meminfo
<mnemoc> maxnet made an installer than patches the SPL of the uSD :p
<libv> mnemoc: what do you suggest for Jef91?
<mnemoc> i don't know, have my brain in gdb :<
<mnemoc> damn TZ diff between life and work
<mnemoc> depends a lot on how confortable he is cross-compiling
<Jef91> I've crossed compiled stuff before and I have a native ARM build machine I use for some packaging work
<libv> that's dealt with in the first steps howto
<Jef91> I'd just been hoping to at least try a pre-built image for the device before diving in to making my own.
<Jef91> So the only way to get up and running on MK802 devices currently is to do all the heavy lifting yourself?
<libv> i wouldn't exactly call that heavy lifting
<mnemoc> if you want the trivial path, try maxnet's installer for android
<mnemoc> if you want to decide what you want and what not, build your own
<Jef91> I just want _any_ functional Linux system on the Mk802 that boots from SD
<libv> http://linux-sunxi.org/MK802 could use some fleshing out
<mnemoc> indeed
<mnemoc> also he mele page
<Jef91> alrighty - thanks for the first steps link libv
<libv> in that there is no mention of how to wire up serial, and that there is no mention that First Steps just works
<Jef91> I'll have to dive into all that later on
<mnemoc> libv: the firststeps page could also be simplified by using sunxi-bsp
<Jef91> am I going to need to break one of my mk802s out of it's case to build the image?
<libv> i believe that that's techn's area, right?
<mnemoc> yes
<hno> Heh... was wondering why JTAG hat lost connection again and then remembered that I had powered off the board to change logic probe connection to a better signal order.
<libv> Jef91: nope, but our standard kernel config and the usual rootfses do not always get you a working system, with working display and networking as is
<libv> i should probably link the fb setup for fb console from first steps as well
<libv> but first i am continuing the clean-up of my lima code
<hno> Jef91, you don't need to open up the mk802 to build & test an image, but if something fails booting you are pretty much blindfolded without serial console.
<Jef91> fair enough hno
<hno> Jef91, so order yourself an 3.3v UART dongle if you don't have one already, then get going on making the image you want to have while the dongle is being delivered.
<hno> I don't remember. Do MK802 have Ethernet or only USB?
<Jef91> USB only hno
<hno> Ok, then as above..
<Jef91> Yep yep.
<Jef91> I guess all the posts on the miniand forums gave me hope I wasn't going to have to do all this for another device. ARM hardware is so much fun /sarcasm
<hno> techn, sata driver corrupts memory if not enabled in script.bin?
<techn> hno: yes.. or enabling it causes some idle time on boot :/
popolon has joined #arm-netbook
<techn> hno: could this be related to clocks? :/
tuliom has joined #arm-netbook
<libv> techn: your configure assumes that boards in sunxi-boards are also in uboot-sunxi
<mnemoc> the happy path :)
<libv> well, build failure later on tells the whole story anyway
<libv> so no big worry
<Jef91> how do I connect to a device via adb?
<Jef91> Can I do it over a network or does it require a hard connection?
<libv> adbd should be installed on your device
<libv> you might need to enable it under developer options somewhere in setup
<libv> usb is preferred
<libv> network usually requires some command line or init stuff
<Jef91> I see a "use debugging" option under developer
<Jef91> in my android settings
<Jef91> that is all I should need?
<drachensun> yup check that
<Jef91> then just hook it into my PC?
<libv> Jef91: url.
<drachensun> and plug it in, yup
<Jef91> hrm
<Jef91> adb shell
<Jef91> is giving me "Device not found"
<libv> and now as root?
<Jef91> running adb shell as root gives: error: device not found
<Jef91> the same
<drachensun> try, adb kill-server then adb devices as root, it will restart the daemon as root
<libv> is it showing up in lsusb?
gimli has quit [Quit: Verlassend]
<Jef91> Wow thats really odd - it isn't libv
<Jef91> But the power light is coming on on the device
<Jef91> so it is getting juice from the port
<libv> then check dmesg
<libv> Jef91: you claim that you've been using this device for a month already
<libv> Jef91: with android on it?
<Jef91> Yea libv
<Jef91> The first mk802 I picked up had a broken SD card slot
<Jef91> I just got a second one in the main
<Jef91> hoping to play with Debian on it
<Jef91> Huh all the "can't find adb device" posts related to ubuntu are going back to 9.10 and older it seems
<drachensun> do you have the udev rules in?
<Jef91> udev rules for what drachensun?
<Jef91> All I did was download and extract the SDK
<libv> ...
<Jef91> and try to run the adb command
<drachensun> ok, check the instructions on that last link I sent
<Jef91> who makes the mk802?
<Jef91> aka what vendor ID should I be using
<libv> lsusb should show something there
<Jef91> lsusb does not show the device
<Jef91> I said that already
<libv> then udev is not going to help
<Jef91> any other suggestions besides googling more?
<libv> 23:38 < libv> then check dmesg
tinti has quit [Ping timeout: 260 seconds]
<Jef91> dmesg doesn't report anything new when I attach the device to my system
focus_it has joined #arm-netbook
<Jef91> tail end of dmesg -> http://paste.debian.net/212869/
<libv> is that you replugging the thing?
<focus_it> I was using my Genesi arm netbook today. Whatever happened to that company? Nothing available to buy in their EU stores and not much news anywhere. It was a very decent netbook but Ubuntu stopped their support for that particular arm and since then its stuck at Ubuntu 10.10.
<Jef91> Seems to be
<Jef91> It is the only device I've been attaching
<libv> Jef91: is that you doing it, or is it doing that on its own?
<Jef91> focus_it: I've actually done some work with the Genesi folks
<steev> focus_it: we're still around, no consumer facing product currently
<Jef91> thats me libv
<mnemoc> focus_it: steev works there
<libv> ok, so then it must be there in lsusb as well
<mnemoc> err
<steev> Jef91: i work as a genesi folk :P
<mnemoc> steev: didn't see you :)
<Jef91> focus_it: if you need a current OS for the Genesi check out my Bodhi image
<Jef91> haha yes steev - the best kind of folks ;)
<steev> mnemoc: i highlight on genesi, efika, and a few others :)
<mnemoc> =)
<focus_it> Jef91: thanks!
<steev> focus_it: fyi, i'm presently working on getting device tree working so we can get a mainline kernel going. part of the issue has been that the arm kernel hasn't been kind to us (lots of flux with different things we needed)
<focus_it> so why they 'still around' and not shining bright say with A10 CPU?
<Jef91> libv: my lsusb outputs this regardless of if it is attached or not -> http://paste.debian.net/212871/
<steev> focus_it: because the a10 is cortex-a8, we're using a9 now, but as i said, no consumer facing product at the moment
<focus_it> so they planning new smartbook? I want one just like the genesi with a sata SSD slot - pleheese!! :-)
<libv> Jef91: does your dmesg tell you the stick is disconnected?
<steev> focus_it: you could always license a design, or have us build one... it will cost about a mil though
<focus_it> Jef91: link for Bodhi image?
<steev> i like the bodhi linux image. more partial to gentoo myself
<focus_it> Jef91: thanks :)
<Jef91> the last line in my dmesg is telling me a USB disconnect
<Jef91> and actually, it keeps adding device numbers
<Jef91> without me plugging/unplugging it
<steev> Jef91: not enough power for the device
<steev> would be my guess
<Jef91> huzzah
<Jef91> power was the issue
<Jef91> I was reaching for the adapter as you said that steev
<Jef91> I thought it could power from just USB
<Jef91> guess Iw as wrong
<focus_it> steev: mil a bit much
<Jef91> Got it.
<Jef91> thanks for putting up with me libv - I'm not always this slow I promise
<steev> focus_it: initial runs aren't cheap :)
<Jef91> and I have lift off I believe....
<Jef91> my USB hub came to life at least... still no picture on the TV though
<focus_it> steev: if stuff I working on make me a spare mil, I be there for mi netbook with ssd :-)
focus_it has quit [Quit: Leaving]
Mehhh has joined #arm-netbook
<steev> :)
hp_ has quit [Read error: Connection reset by peer]
hp_ has joined #arm-netbook
<Gumboot> Jef91: I hope you've learnt not to speak ill of the pi, now... Everyone who does gets flooded with vacuous "it's for education" comments.
<Jef91> haha Gumboot if I can get Debian rolling on the MK802 I will continue pushing it over the Pi.
<Jef91> Having used both the mk802 is just a better device.
<Jef91> Pff not to mention the most recent raspbian update seems to have massively f***ed my TV setting
<Jef91> Nice of the devices are truly open source - so I'm confused as to why everyone flocked to the pi so much
<Gumboot> Since you have to attach USB everything to the pi to make it in any way useful (looking at mpd people attaching USB audio, even), you might as well counter that you could attach phidgets to the mk802.
<Gumboot> I don't know if you actually can.
<Gumboot> I don't think that's important, though.