| 00:49.28 | *** join/#arm-netbook QingPei (~qingpei@114.241.180.108) |
| 03:01.46 | *** join/#arm-netbook destinal (~chatzilla@ip68-108-26-102.lv.lv.cox.net) |
| 03:32.12 | destinal_ | mnemoc: well, if they use eoma68 without the connector than they're also not infringing the patent because the patent is about connector reuse, right? |
| 03:32.38 | destinal_ | err lkcl ^ |
| 08:57.37 | CIA-91 | rhombus-tech: Carlos master * r05e2d5d7dc2a /allwinner_a10/orders/charlie__95__mtz.mdwn: |
| 10:24.35 | zenitraM | hates the fact that China Post tracking only works properly during China daytime hours |
| 11:28.08 | mnemoc | zenitraM: hi, did you try to remove the black headers of the jumper cable to connect the mele to your ttl/usb adapter? |
| 11:30.16 | mnemoc | mutilating 4 now |
| 11:37.54 | mnemoc | they are very very close, but not touching... Tx and 3.3V get like 0.5mm away each other |
| 11:45.41 | mnemoc | feels hardcore :p |
| 11:46.05 | mnemoc | .oO(that's lame but true)o |
| 11:51.26 | *** join/#arm-netbook techman2 (~gj@121.209.129.135) |
| 11:53.56 | zenitraM | mnemoc: what i did is |
| 11:54.00 | zenitraM | plug gnd and.. rx? |
| 11:54.26 | zenitraM | and then use a cable (inserted on the jumper wire) to wrap around tx |
| 11:55.16 | mnemoc | tried uboot-spl-mmc on the mele? |
| 11:55.27 | zenitraM | yup |
| 11:55.29 | zenitraM | it worked |
| 11:55.34 | mnemoc | amazing |
| 11:55.36 | mnemoc | :D |
| 11:56.03 | zenitraM | in fact it was the only way i found to boot without boot1 |
| 12:01.08 | CIA-91 | rhombus-tech: Valentijn master * rca30b3d5aca5 /allwinner_a10/orders/valentijnsessink.mdwn: |
| 12:09.12 | *** join/#arm-netbook hipboi (~hipboi@222.50.109.31) |
| 12:14.59 | lkcl | destinal_: correct. |
| 13:56.56 | hipboi | anyone get the touch screen working under X? |
| 14:08.33 | CIA-91 | rhombus-tech: lkcl master * rdc6520dddb5c /allwinner_a10/orders/charlie__95__mtz.mdwn: order processing cleanup |
| 14:47.43 | mnemoc | dumb electrical question, my ttl/usb has 5 pins and a switch (3 pins and a jumper), in one position of the jumper I get 5V comparing G and Tx, but on the other position I get 3.9V... does that count as 3.3V :-/ ... the 3.3V pin gives 3.3V flat |
| 14:51.20 | tjoy | tolerance for 3.3v inputs is usually up to 3.6v, but i think you're probably doing it wrong |
| 14:52.05 | mnemoc | could the switch be anything else but a V selector? |
| 14:52.16 | tjoy | not sure |
| 14:52.53 | zenitraM | it is probably the one for 3.9V |
| 14:52.59 | zenitraM | although.. mmm i'm going to measure mine |
| 14:54.18 | zenitraM | 3.08v for me |
| 14:54.37 | mnemoc | :( |
| 14:54.50 | mnemoc | then I better don't use this dongle |
| 14:55.00 | zenitraM | where did you get it from? |
| 14:56.21 | mnemoc | http://cgi.ebay.es/ws/eBayISAPI.dll?ViewItem&Item=170728559489 |
| 14:57.38 | mnemoc | oddly if I jump the two closer to the 3.3V pin I get 5V on Tx |
| 14:57.42 | zenitraM | try removing the jumper |
| 14:58.03 | mnemoc | removing the jumper, or jumping the other two (closer to the 5V pin) I get 3.9 |
| 14:58.45 | zenitraM | and what do you get between gnd and 3.3v? |
| 14:59.25 | mnemoc | 3.36V |
| 15:00.17 | zenitraM | idk, logic tells me it should be the 3.9V :/ |
| 15:00.54 | mnemoc | :( |
| 15:01.10 | zenitraM | this one has instructions: http://www.wvshare.com/img/devkit/accBoard/PL2303-USB-UART-Board-mini/PL2303-USB-UART-Board-mini-2.jpg |
| 15:01.45 | zenitraM | and it seems the jumper is indeed for power |
| 15:04.11 | mnemoc | oh |
| 15:04.39 | mnemoc | in one position of the jumper G vs. Rx gives 3.3V |
| 15:05.12 | mnemoc | *headdesk* |
| 15:05.57 | zenitraM | there you go |
| 15:06.02 | mnemoc | shouldn't Rx be 0.0 when not connected? |
| 15:06.29 | mnemoc | or Rx becomes a 3.3 Tx? |
| 15:06.35 | mnemoc | puzzled |
| 15:07.02 | zenitraM | mine is also 3.3 |
| 15:07.14 | zenitraM | Rx marks on the dongle = Rx for device |
| 15:07.17 | zenitraM | (RXD) |
| 15:07.33 | zenitraM | so that should be the port where the computer *transmits*, if i'm not wrong |
| 15:09.08 | mnemoc | when Rx is 3.3V, Rx vs. Tx gives me 0.5V ... does that make sense? |
| 15:09.59 | mnemoc | following the logic of dongle's Rx been the output of the dongle, shouldn't Tx be 0V? |
| 15:10.17 | mnemoc | awfully puzzled by his ignorance |
| 15:26.16 | zenitraM | mnemoc: stop thinking and plug it. |
| 15:26.53 | mnemoc | i don't want to burn my cute mele :( |
| 15:31.35 | mnemoc | well... I can still add myself to the second batch if it goes wrong |
| 15:45.35 | mnemoc | no smoke, good sign :) |
| 16:01.50 | mnemoc | but it seems my hdmi display died... :( |
| 16:12.39 | mnemoc | for my own sake I hope it was natural death... killing a TFT is not nice at all :-/ |
| 16:13.26 | mnemoc | a divine signal to tell me to focus on $work$ and not fun |
| 16:21.35 | zenitraM | mnemoc: don't panic |
| 16:21.39 | zenitraM | did you press any button on the remote? |
| 16:24.01 | zenitraM | there's a button to toggle between video outputs. |
| 16:25.14 | mnemoc | the power led of the display doesn't light anymore |
| 16:25.35 | zenitraM | the front led? |
| 16:25.42 | mnemoc | yup |
| 16:25.59 | mnemoc | connected it to other hdmi devices to test too |
| 16:26.01 | mnemoc | it died |
| 16:26.11 | mnemoc | no clue why |
| 16:26.17 | zenitraM | does unplugging and plugging do anything? |
| 16:26.38 | zenitraM | :S |
| 16:26.50 | zenitraM | ah |
| 16:26.54 | zenitraM | the TFT |
| 16:28.53 | mnemoc | yes, the TFT |
| 16:30.13 | zenitraM | thought it was the mele |
| 16:30.21 | zenitraM | but well, that's weird |
| 16:30.27 | mnemoc | mele was cheaper :p |
| 16:32.58 | mnemoc | btw, does one need to modify files in nanda to boot from the sd or it's done purely by boot0 magic? |
| 16:33.33 | zenitraM | nope |
| 16:33.48 | zenitraM | boot0 magic. it can even boot on faulty devices :P |
| 16:33.57 | mnemoc | neat |
| 16:57.00 | specing | My tablet ran out of battery and now it won't boot anymore |
| 16:57.02 | specing | :( |
| 16:57.19 | zenitraM | are you charging it via usb? |
| 16:58.35 | specing | no, charger |
| 16:59.28 | specing | the splash screen comes up (droid holding his arms crossed), but it never goes beyond that |
| 17:00.17 | zenitraM | mmm try rebooting or reflashing the firmware |
| 17:04.00 | specing | I don't even know where the serial port is |
| 17:04.18 | specing | I've been chrooting until now |
| 17:16.54 | zenitraM | no need to serial port |
| 17:17.18 | zenitraM | just get the original firmware, livesuit or phoenixcard, and a windows machine |
| 17:17.48 | zenitraM | with livesuit you can flash directly through USB after you enter on the FEL mode (usually by pressing a key or with a recovery button on the tablet) |
| 17:17.56 | zenitraM | with phoenix card you can create a bootable sd that reflashes the fw |
| 17:19.39 | specing | I want the serial port for my own use |
| 17:20.09 | specing | Maybe its just running lots of fscks in the background |
| 17:20.18 | specing | since I left all the partitions mounted |
| 17:20.19 | zenitraM | mmm you can use adb |
| 17:20.26 | zenitraM | to get a shell through usb |
| 17:20.48 | specing | I want the _real_ serial port since I'll be putting my own kernel up there |
| 17:20.58 | specing | I can't stand the android one |
| 17:21.12 | specing | I mean, some things are nice, such as /dev/block convention |
| 17:59.10 | zenitraM | specing: to get a real serial port you can use a sd breakout board |
| 17:59.17 | zenitraM | anyway, adb doesn't require the android kernel |
| 17:59.24 | zenitraM | in fact it works with only copying the adb binary |
| 17:59.53 | zenitraM | but anyway i meant that you could try using adb to see why it doesn't boot |
| 18:47.18 | specing | Where do I get this livesuit though? And can it work without a network connection? |
| 19:30.27 | *** join/#arm-netbook arokux (~arokux@merkur178.inf.uni-konstanz.de) |
| 19:53.09 | CIA-91 | rhombus-tech: Miquel_Angel master * ra75ace3f5149 /allwinner_a10/orders/mmestres.mdwn: |
| 20:04.14 | zenitraM | specing: yes |
| 20:04.21 | zenitraM | look around slatedroid forums |
| 20:04.30 | zenitraM | it is usually included with the firmwares |
| 20:11.41 | specing | <silly q.> What if I do not have the vol- button? </silly q.> |
| 20:15.05 | CIA-91 | rhombus-tech: lkcl master * r51a3522eeaf7 /community_ideas/educational_and_games_mc.mdwn: add hugo s.america educational/games machine |
| 20:15.15 | CIA-91 | rhombus-tech: lkcl master * r033d0b74dcdb /: Merge branch 'master' of ssh://git.hands.com/rhombus |
| 20:22.39 | mnemoc | lkcl: btw, when hugo meneses said "resume" (from the spanish "resumir", another false friend between both languages) he meant "summarise" |
| 20:23.12 | lkcl | ahh |
| 20:25.14 | *** part/#arm-netbook coreboot|QingPei (~qingpei@114.241.180.108) |
| 20:26.04 | hno | specing, there is probably a small pinhole for recovery, forcing FEL mode. |
| 20:28.23 | hno | mnemoc, odd with those voltages. Did it work? |
| 20:29.46 | mnemoc | didn't get any output but at least neither the dongle nor the mele got fried |
| 20:31.43 | mnemoc | are you familiar with hipboi's uboot-mmc ? |
| 20:32.54 | mnemoc | can you hint me how to make it drop a prompt on that uart (and stay there!) ... I've never used uboot before :( |
| 20:35.41 | mnemoc | i need to confirm the console over usb is working... and the display I have for playing decided to die so I don't have how to check if android is booting or if uboot is holding it |
| 20:37.47 | hno | u-boot does not show anything on display I think. |
| 20:38.37 | hno | if you boot the mmc uboot then it should stay at u-boot prompt. |
| 20:39.31 | mnemoc | ok, so if i didn't see anything tried both convinations of rx/tx i fried something or the mmc uboot is set to use a different port, right? |
| 20:40.09 | hno | the MMC u-boot should be set to use the standard UART by default. |
| 20:40.29 | mnemoc | then I fried something, narf :( |
| 20:40.54 | hno | Testing the dongle is simple. Just connect tx+rx and it should echo back anything you type. |
| 20:41.11 | mnemoc | nice |
| 20:41.28 | mnemoc | puts $work$ out of the table and switches to learning mode |
| 20:45.41 | mnemoc | meh, no echo |
| 20:47.23 | hno | odd. Usually quite hard to crash those dongles. |
| 20:51.26 | mnemoc | in one position of the switch I get the echo |
| 20:51.38 | mnemoc | I'll check it's voltages |
| 20:51.51 | hno | no documentation on what that switch does? |
| 20:52.08 | hno | any board markings next to it? |
| 20:52.26 | mnemoc | nothing |
| 20:52.39 | hno | you can check the voltage level with Rx&Tx connected together. Reduces confusion a bit. |
| 20:53.20 | specing | hno: there is! |
| 20:53.37 | hno | receive pin may float a bit and give odd readings. |
| 20:54.25 | mnemoc | hno: http://www.ebay.com/itm/170728559489 <-- pictures of the switch |
| 20:54.55 | hno | I saw that earlier, but no good pictures there. |
| 20:54.56 | mnemoc | hno: rx vs tx is 0.5v |
| 20:55.41 | hno | not meaningful to measure between rx & tx. Connect rx & tx together and then measure to gnd. |
| 20:56.07 | mnemoc | ah, ok |
| 20:56.48 | hno | by connecting them together you rule out any confusion on which is tx and which is rx, and can focus on I/O voltage level. |
| 20:58.35 | mnemoc | 3.33V :D |
| 20:58.43 | hno | next is finding which is tx. That can be done by measuring one pin to gnd and seding breaks. |
| 20:58.45 | mnemoc | and echo is working |
| 20:58.54 | hno | how to send a break varies depending on your terminal program. |
| 20:59.55 | hno | which terminal program are you using? |
| 21:00.09 | mnemoc | gtkterm, I see a menu option that says send break |
| 21:00.41 | hno | You should be able to measure a drop to 0 when sending break. |
| 21:01.16 | hno | to ease measuring set baud rate as low as possible. |
| 21:02.16 | hno | i.e. 300 bps or similar. |
| 21:02.20 | mnemoc | hates his motor skills |
| 21:03.25 | hno | Ctrl-S for port settings. TAB to move between fields. Arrows to change. |
| 21:03.49 | hno | hates mouse |
| 21:04.02 | mnemoc | the hard part is to hold the ... sticks... of the multitester |
| 21:04.31 | hno | just tape wires to it? |
| 21:04.44 | mnemoc | uh |
| 21:04.47 | mnemoc | 1m |
| 21:05.13 | hno | Tape wires or needles to the sticks and connect the cables. No need to hold. |
| 21:06.21 | hno | holding just risks shorting something. |
| 21:07.26 | hno | if you have some metal wire then you can easily make a pin taped to the multimeter stick, allowing you to connect cables easily. |
| 21:08.47 | hno | a paper clip is a good source of metal wire. |
| 21:08.59 | mnemoc | yes, using that |
| 21:11.12 | hno | but if you just measure then the pin which is 3.33V should be TX. The pin which have some other voltage should be RX. |
| 21:11.26 | hno | the measurement of break can confirm 100% |
| 21:11.59 | mnemoc | Tx to G is 3.9V, Tx+Rx to G is 3.3V |
| 21:12.13 | hno | Rx to G? |
| 21:13.26 | hno | bets on 3.3V |
| 21:13.37 | mnemoc | Rx falls near 0 when sending breaks |
| 21:13.57 | mnemoc | yes, 3.3V :) |
| 21:13.59 | hno | Great. So your board has Rx & Tx markings switched. |
| 21:14.39 | mnemoc | yes :) |
| 21:15.02 | mnemoc | I'll re create the uboot-mmc sd card now |
| 21:15.28 | hno | So connect Tx & Gnd to the mele Tx and GND. Then boot u-boot. You should see output. |
| 21:15.50 | hno | leave Rx unconnected until you have found output. |
| 21:16.28 | hno | If you do not see any output then you can try moving the Tx cable to Rx on the mele in case the drawing have them labelled the other way aorund. |
| 21:16.51 | hno | The receive pin of the dongle can be connected freely anywhere without risk, as long as GND is right. |
| 21:17.26 | hno | Tx = Receive pin on your dongle.. |
| 21:17.55 | mnemoc | yes |
| 21:17.59 | mnemoc | 1m |
| 21:18.27 | hno | When you see output from U-boot then connect the other and you should be able to type as well. |
| 21:18.48 | hno | If you see garbage then pin is right but baud rate is wrong. |
| 21:20.51 | hno | I think the mele expects 115200 as baud rate. |
| 21:25.27 | zenitraM | also |
| 21:25.33 | zenitraM | the mele uses u-boot internally |
| 21:25.46 | zenitraM | you should see the stock u-boot (and be able to interrupt it) when booting normally |
| 21:26.23 | zenitraM | while on android, there's sh running on the serial console so you should also be able to run commands |
| 21:27.08 | zenitraM | you can boot kernels on nand with the built-in uboot |
| 21:27.08 | hno | right, the mele firmware left the debug console on by default. |
| 21:29.06 | hno | mnemoc, any progress? |
| 21:29.25 | mnemoc | nothing... |
| 21:29.45 | hno | :( |
| 21:30.00 | mnemoc | sd card remade, Tx and Gnd connected, gtkterm listening... and silence |
| 21:30.19 | hno | which baud rate is selected? |
| 21:30.19 | mnemoc | the led of the mele is purple |
| 21:30.24 | mnemoc | 115200 |
| 21:30.33 | zenitraM | try booting without the sd. also, is tx connected to your dongle's tx? |
| 21:31.00 | mnemoc | G and Tx according to http://rhombus-tech.net/allwinner_a10/hacking_the_mele_a1000/A10_device_a1000_inside.jpg |
| 21:31.10 | mnemoc | Tx to Tx and G to G |
| 21:31.37 | zenitraM | try unplugging and replugging the usb dongle |
| 21:31.52 | zenitraM | sometimes accidental shorts cause it to hang |
| 21:31.55 | hno | or just do the echo test again. |
| 21:32.46 | hno | echo test is better, as it verifies the whole chain, except for baud rate. |
| 21:33.32 | hno | zenitraM, is the picture labelled right? With Tx as transit signal from mele? |
| 21:33.59 | zenitraM | yes, afaik |
| 21:34.20 | zenitraM | i received the output by just plugging G and Tx (no room to fit the Rx jumper wire) |
| 21:34.28 | mnemoc | ttried swapping Tx/Rx on the mele and power cycled it.... no luck |
| 21:34.40 | mnemoc | will try without the sd card now |
| 21:35.27 | zenitraM | also, the marks on the dongle are reversed because, at least on mine, it says RXD and TXD, meaning... this goes to RX on the device |
| 21:35.47 | hno | we have already identified the signals on the dongle |
| 21:36.12 | hno | and it is reversed. |
| 21:36.31 | mnemoc | mele powered without the SD, led is blue, nothing on the term |
| 21:36.45 | hno | different led color? |
| 21:37.19 | mnemoc | when trying with mmc uboot on the SD led was purpleish |
| 21:38.26 | zenitraM | mmm i didn't notice that when testing. but it could be |
| 21:38.44 | zenitraM | try the loop test.. also plug/replug and close/open the term |
| 21:38.53 | hno | that's a good sign at least. But no idea why you get no output. |
| 21:41.35 | mnemoc | echo is working without reconnecting the dongle |
| 21:42.02 | zenitraM | then something might be wrong with the connections... |
| 21:43.35 | mnemoc | maybe my SD is too big (16GB) ... I'll find a 2GB I have somewhere and do http://rhombus-tech.net/a10_mmc_boot/ again |
| 21:43.56 | hno | mnemoc, you should not need an sd card at all. |
| 21:44.14 | mnemoc | uhm |
| 21:47.06 | hno | ? |
| 21:47.32 | mnemoc | trying again without sd but with the connectors on the mele more tight |
| 21:47.53 | hno | you can also try angling them slightly. |
| 21:48.36 | hno | it's quite thin pins in the uart connector. |
| 21:50.27 | mnemoc | still silence :-/ |
| 21:52.35 | mnemoc | sure the default bootloader will greet me on this uart? |
| 21:53.56 | mnemoc | and the loop test still works, so the dongle is not hang |
| 21:54.02 | mnemoc | hung* |
| 21:55.51 | hno | annoying |
| 21:59.40 | mnemoc | frustrating |
| 22:04.02 | zenitraM | mnemoc: it should greet, 100% sure of that |
| 22:04.14 | zenitraM | android should also output kernel logs |
| 22:04.38 | zenitraM | the only thing i think could be wrong is.. cables |
| 22:04.51 | zenitraM | try to short the rx and tx cables on the part that should go to the mele |
| 22:04.58 | zenitraM | and try the test then |
| 22:05.05 | mnemoc | ok |
| 22:05.30 | zenitraM | even boot1 outputs to the serial |
| 22:05.31 | hno | zenitraM, he have already done loop/echo testing many times. Cables works fine. |
| 22:06.03 | zenitraM | hno: but he's done the test with the cables or just shorting the dongle's pins? that's the difference |
| 22:06.16 | hno | mnemoc? |
| 22:06.41 | mnemoc | the loop i've done it with a single f/f jumper cable |
| 22:06.51 | mnemoc | will test the long way now |
| 22:08.24 | hno | zenitraM, Is the USB connector also 2mm? |
| 22:08.59 | zenitraM | not sure of which is each, but the USB has the bigger one |
| 22:09.09 | zenitraM | oh, you mean |
| 22:09.11 | zenitraM | the one on the mele? |
| 22:09.14 | hno | yes. |
| 22:09.22 | zenitraM | i think it was the same as the serial |
| 22:10.22 | mnemoc | the usb is 2.54, the mele is 2mm |
| 22:10.48 | hno | mnemoc, I am talking about the device USB connector within the mele. |
| 22:10.52 | mnemoc | but removed the black headers and compressed the metallic header a bit to make them tight |
| 22:11.14 | mnemoc | only the sata power is o.1" |
| 22:12.08 | zenitraM | on the script.bin there are configurations about the working mode of each usb |
| 22:13.00 | zenitraM | it might be possible to turn one of the external usbs to be usb gadget. not sure if this is electrically viable anyway |
| 22:13.24 | zenitraM | tablets use the same usb as host and gadget |
| 22:13.43 | hno | zenitraM, I need the A10 port, not a hub port. Looking into getting FEL mode running on the mele. |
| 22:14.34 | zenitraM | mm, ok then |
| 22:14.54 | hno | I kind of hope that the fifth pin in the USB device connector is the FEL boot selector pin. But remains to be tried. |
| 22:15.13 | mnemoc | for the records, tested a long loop with the 4 wires and works good :( |
| 22:15.21 | zenitraM | it could be |
| 22:15.36 | zenitraM | mmm then it might not be making contact properly with the serial... |
| 22:16.32 | mnemoc | i've pushed them on diagonal to force a connection too |
| 22:17.19 | mnemoc | but it seems I'll gave to wait for the real 2.0 to 2.54 cables :'( |
| 22:18.25 | hno | If you look straight into the cable contacts there should be metal springs making contact with mostly anything that fits |
| 22:20.16 | mnemoc | the m/m jumper cable I used to test the loop fits very tightly |
| 22:20.52 | mnemoc | my dvi/vga 15" tft revived \o/ |
| 22:21.08 | mnemoc | and android is there |
| 22:21.14 | mnemoc | good, it's not fried |
| 22:21.54 | mnemoc | but why didn't I see any kernel log :-/ |
| 22:22.07 | mnemoc | *headdesk* |
| 22:26.33 | mnemoc | testing the pins of the mele in the same way we tested the dongle |
| 22:27.11 | zenitraM | do you have an android serial client for that? |
| 22:27.49 | hno | with multimeter you should se gnd, some voltage, 3.3v, 3.3v. |
| 22:28.13 | mnemoc | i was going to check voltages, not sending breaks |
| 22:28.28 | zenitraM | ah |
| 22:29.19 | hno | not much you can see with a multimeter. |
| 22:30.02 | mnemoc | at least I can discard problems |
| 22:30.33 | hno | you can basically only identigy the GND and V3.3 pins. Not which is RX or TX. |
| 22:31.24 | hno | if you have a root shell then you can do a loop test from the mele as well. |
| 22:31.56 | hno | if you figure out the android device name for ttyS0 |
| 22:32.13 | zenitraM | i think it was ttyS0 too |
| 22:32.51 | hno | if you find it, then first "kill -STOP <pidofconsoleshell>", then |
| 22:32.56 | hno | cat /dev/ttyS0 & |
| 22:33.02 | hno | echo hello >/dev/ttyS0 |
| 22:33.48 | hno | with tx & rx on the mele shorted. |
| 22:34.45 | hno | but you really should have a small valued resistor for testing shorting like this. |
| 22:35.00 | mnemoc | G vs any other pin gives me 3.3V, but Tx+Rx vs G gives me 1V.... |
| 22:35.49 | hno | then loop test probably works.. |
| 22:36.03 | hno | with the shell talking to itself. |
| 22:36.37 | hno | and multimeter confused. |
| 22:37.04 | hno | if you kill -STOP the console shell then should be stable 3.3V |
| 22:39.28 | hno | need to go to bed. Hope you figure it out. |
| 22:40.38 | mnemoc | my idea was to completely ignore the included android and focus in getting the ported kernel working... |
| 22:40.56 | hno | is also not too interested in Android. |
| 22:41.16 | zenitraM | would swapping tx and rx cause any damage? |
| 22:51.52 | CIA-91 | rhombus-tech: Mads master * rb08f773f76ae /allwinner_a10/orders/powerage.mdwn: |
| 22:52.07 | mnemoc | hope not |
| 22:55.43 | ManoftheSea | Man, if everyone buys a mele, no one will want an EOMA |
| 22:59.16 | steev | not true at all |
| 22:59.32 | steev | some of us love collecting hardware |
| 23:00.12 | hno | zenitraM, there is no risk to connect the dongle receive pin (TX) to any pin on the mele. |
| 23:01.25 | hno | but may not be entirely healty to connect the dongle transmit pin (Rx) to the mele Tx pin. |
| 23:02.23 | hno | ManoftheSea, the mele is fun, but at least for me it does not compete with EOMA. |
| 23:02.54 | hno | quite different beasts, even if there is similarities. |
| 23:07.50 | ManoftheSea | I know. Just getting impatient |
| 23:44.09 | *** join/#arm-netbook menomc (~amery@shell.opensde.net) |
