| 01:13.22 | *** join/#arm-netbook mikey_w (~mike@c-71-63-115-202.hsd1.va.comcast.net) |
| 01:13.41 | *** join/#arm-netbook mike_ (~mike@c-71-63-115-202.hsd1.va.comcast.net) |
| 01:20.57 | steev_ | mnemoc: actually Konstantinos (the main Debian developer behind armhf) is a Genesi employee. it's been armhf ready for quite a while |
| 01:33.24 | *** join/#arm-netbook Eigen (~Eigen@S0106b8c75dc9a198.vn.shawcable.net) |
| 02:56.32 | *** join/#arm-netbook Eigen (~Eigen@S0106b8c75dc9a198.vn.shawcable.net) |
| 05:50.17 | *** join/#arm-netbook A0Sheds (~ly@adsl-75-49-211-164.dsl.emhril.sbcglobal.net) |
| 05:50.17 | *** join/#arm-netbook A0Sheds (~ly@unaffiliated/l84supper) |
| 06:00.37 | A0Sheds | the road is actually pretty short from eoma68 card to laptop since there's already firmware for EC's on ARM cortex m3 |
| 06:15.32 | *** join/#arm-netbook Charlie (~quassel@64.31.59.70) |
| 06:48.19 | *** join/#arm-netbook mikey_w (~mike@c-71-63-115-202.hsd1.va.comcast.net) |
| 06:48.39 | *** join/#arm-netbook mike_ (~mike@c-71-63-115-202.hsd1.va.comcast.net) |
| 07:11.36 | *** join/#arm-netbook cjoe (~customerj@86FF5B78.mobile.pool.telekom.hu) |
| 08:04.29 | *** join/#arm-netbook cjoe (~customerj@95C8473D.mobile.pool.telekom.hu) |
| 08:26.20 | CIA-158 | rhombus-tech: Nataraj master * r8850c811ec9b /index/discussion.html: |
| 08:26.58 | *** join/#arm-netbook eebrah (~Ibrahim_K@212.49.88.78) |
| 08:31.13 | specing | A0Sheds: there are SMPS and battery circuits to be done |
| 09:07.01 | *** join/#arm-netbook sponix (~sponix@c-98-244-187-216.hsd1.ga.comcast.net) |
| 09:25.21 | specing | A0Sheds: Probably the most difficult thing to do would be to choose a case |
| 09:28.32 | *** join/#arm-netbook eebrah (~Ibrahim_K@212.49.88.78) |
| 09:56.37 | *** join/#arm-netbook lkcl_ (~lkcl@host86-131-178-131.range86-131.btcentralplus.com) |
| 10:05.52 | mnemoc | hopes you don't pick one of those bending plastic crappy netbook cases |
| 10:11.22 | specing | :) |
| 10:11.51 | mnemoc | is a thinkpad fanboy |
| 10:19.46 | specing | I associate "thinkpad" with old crap |
| 10:20.17 | mnemoc | I associate it with heavy usage laptop |
| 10:21.10 | mnemoc | programmer-proof |
| 11:01.28 | CIA-158 | rhombus-tech: Marcin_Piotr master * r9ea33c32b2f5 /allwinner_a10/orders/mpp.mdwn: |
| 11:02.19 | specing | Lmao, I made my phone boot |
| 11:02.33 | specing | internal nand seems to be fscked up |
| 11:15.29 | specing | Good thing it has the fastboot interface |
| 11:21.17 | mnemoc | sad fastboot only provides flashing and not dumping |
| 11:21.42 | mnemoc | it would make backing up much easier |
| 11:26.57 | specing | you can boot via mmc (as I have done in this case (from previous backups)) and dump flash from there |
| 11:27.14 | specing | my original backups were from rooted android (rsync) |
| 11:27.25 | mnemoc | sure, but not all fastboot-capable devices can do that :) |
| 11:27.33 | mnemoc | a10 is blessed in that sense |
| 11:27.33 | specing | there is a rsync armv5tel binary on my site if anyone needs it |
| 11:27.56 | specing | my phone is Qualcomm MSM |
| 11:28.08 | mnemoc | and boot from mmc??? |
| 11:28.09 | specing | 600MHz ARMv6 |
| 11:28.12 | mnemoc | boots* |
| 11:28.26 | specing | No, I mounted mmc filesystems from initramfs |
| 11:28.45 | mnemoc | nice trick |
| 11:28.49 | specing | :) |
| 11:29.28 | specing | Now it says: "Blank SD card: SD card blank or has unsupported filesystem" |
| 11:29.59 | mnemoc | narf |
| 11:30.23 | specing | Silly android, ext2 is supported |
| 11:31.19 | specing | Now I have to figure out how to build adb here, since 'lunch' isn't cooperating without javac |
| 11:31.54 | mnemoc | specing: for ubuntu linaro provides a ppa with it |
| 11:32.21 | specing | ppa? |
| 11:32.46 | mnemoc | third-party repository hosted by canonical |
| 11:32.46 | specing | Eh |
| 11:32.55 | specing | Im a Gentoo nerd, I build everything myself |
| 11:33.15 | mnemoc | :) |
| 11:34.40 | specing | I see it will be hard to trick the build system to believe I have java installed |
| 11:34.43 | specing | You are attempting to build with the incorrect version |
| 11:34.45 | mnemoc | so be helpful with the portage people and make real adb and fastboot packages ;-) |
| 11:34.45 | specing | of java. |
| 11:34.48 | specing | Your version is: 1.6. |
| 11:34.50 | specing | The correct version is: 1.6. |
| 11:35.32 | specing | But that would require me to learn to write ebuilds!! |
| 11:35.34 | mnemoc | having to grab the whole sdk or android build system just to get adb isn't nice |
| 11:35.39 | specing | True |
| 11:35.40 | mnemoc | specing: so? |
| 11:35.44 | specing | Well |
| 11:35.47 | specing | No time :( |
| 11:35.50 | specing | :P |
| 11:36.00 | mnemoc | no time and using gentoo?? uhm... |
| 11:36.28 | specing | well |
| 11:36.36 | specing | I'll have some time after finals |
| 11:36.42 | specing | That is if: |
| 11:36.47 | specing | - I pass this year |
| 11:36.50 | mnemoc | gentoo was made for people with excess of spare time and loving to play with different kinds of fancy gcc flags |
| 11:36.51 | specing | - I pass finals |
| 11:37.14 | specing | I have been using Gentoo for 3 years now ;) |
| 11:37.38 | mnemoc | and still haven't learn to make ebuilds? lame |
| 11:37.40 | specing | I actually had a lot of time back then |
| 11:37.41 | mnemoc | j/k |
| 11:38.01 | specing | Well GCC had a lot of fancy flags.. j/k |
| 11:39.39 | mnemoc | :) |
| 11:41.08 | mnemoc | not even long over a decade ago when I was an LFS fan I cared about gcc flags :p |
| 11:42.44 | specing | You can build fastboot by cd'ing to its source directory and doing: |
| 11:42.46 | specing | gcc -o fastboot usb_linux.c util_linux.c fastboot.c protocol.c engine.c bootimg.c -lz ../libzipfile/zipfile.c ../libzipfile/centraldir.c -I../include -I../libzipfile -I../mkbootimg |
| 11:43.01 | specing | I still have to figure out adb |
| 11:43.01 | CIA-158 | rhombus-tech: vmoskv master * r5688f31ad91a /allwinner_a10/orders/Vincentpgp.mdwn: |
| 11:57.28 | hno | destinal, you also need a screeen. |
| 11:59.56 | specing | Yay, it built adb for me after I commented 40 lines from its makefile |
| 12:03.32 | ManoftheSea | mnemoc: I thought building LFS *caused* you to care about GCC flags. |
| 12:03.47 | ManoftheSea | like -o9, and -arch=SUPAFAST |
| 12:03.55 | mnemoc | nope, that's gentoo |
| 12:03.58 | specing | :) |
| 12:04.00 | ManoftheSea | oh. ricers. |
| 12:04.03 | specing | -O666 here |
| 12:04.10 | mnemoc | LFS makes you care about choosing the packages correctly :) |
| 12:04.24 | ManoftheSea | yeah. and some packages are fast updating. |
| 12:04.39 | ManoftheSea | So you can no longer find them. I'm glad LFS hosts them. |
| 12:04.49 | mnemoc | :) |
| 12:11.32 | specing | Now where did I put that psneuter binary.... hmm |
| 12:39.11 | *** join/#arm-netbook destinal (destinal@cryptkcoding.com) |
| 12:39.41 | *** join/#arm-netbook dyoung-away (dyoung@cryptkcoding.com) |
| 12:39.54 | *** join/#arm-netbook dyoung (dyoung@nasadmin/dyoung) |
| 12:40.32 | *** join/#arm-netbook ka6sox (ka6sox@nasadmin/ka6sox) |
| 13:33.47 | *** join/#arm-netbook destinal (destinal@cryptkcoding.com) |
| 13:34.17 | *** join/#arm-netbook dyoung-away (dyoung@cryptkcoding.com) |
| 13:34.30 | *** join/#arm-netbook dyoung (dyoung@nasadmin/dyoung) |
| 13:35.08 | *** join/#arm-netbook ka6sox (ka6sox@cryptkcoding.com) |
| 13:35.09 | *** join/#arm-netbook ka6sox (ka6sox@nasadmin/ka6sox) |
| 14:12.29 | *** join/#arm-netbook A0Sheds (~ly@adsl-75-49-211-164.dsl.emhril.sbcglobal.net) |
| 14:12.29 | *** join/#arm-netbook A0Sheds (~ly@unaffiliated/l84supper) |
| 14:22.42 | *** join/#arm-netbook destinal (destinal@cryptkcoding.com) |
| 14:23.11 | *** join/#arm-netbook dyoung-away (dyoung@cryptkcoding.com) |
| 14:23.25 | *** join/#arm-netbook dyoung (dyoung@nasadmin/dyoung) |
| 14:24.06 | *** join/#arm-netbook ka6sox (ka6sox@cryptkcoding.com) |
| 14:24.07 | *** join/#arm-netbook ka6sox (ka6sox@nasadmin/ka6sox) |
| 15:50.03 | A0Sheds | http://hardware.slashdot.org/story/12/04/30/1329254/intel-unveils-tiny-next-unit-of-computing-to-match-raspberry-pi |
| 15:50.18 | A0Sheds | http://www.extremetech.com/extreme/127903-watch-out-raspberry-pi-intel-unveils-ultra-small-next-unit-of-computing-pc |
| 15:51.05 | A0Sheds | NUC is a complete 10x10cm (4x4in) Sandy Bridge Core i3/i5 computer. On the back, there are Thunderbolt, HDMI, and USB 3.0 ports. |
| 15:51.47 | A0Sheds | price point around $100 would be realistic. |
| 15:52.04 | mnemoc | you can hardly see the PCB with all that junk... |
| 15:53.14 | mnemoc | still, competition is good :) |
| 15:53.34 | mnemoc | but why comparing it with a r-pi??? |
| 15:53.35 | specing | x86 vs ARM is hardly competition |
| 15:53.56 | specing | x86 sucks |
| 15:56.46 | mnemoc | A0Sheds: btw, are there green areas in your eoma68 modules? :) |
| 16:00.59 | mnemoc | A0Sheds: how does that core with the amd e350/e450 you where considering for the x86 eoma68 module? |
| 16:01.15 | mnemoc | s/with/compare with/ |
| 16:01.37 | mnemoc | meh, coffee... |
| 16:07.02 | A0Sheds | http://www.amd.com/US/PRODUCTS/NOTEBOOK/APU/Pages/tablet.aspx#3 |
| 16:07.12 | A0Sheds | http://rhombus-tech.net./amd_g_series/ |
| 16:07.21 | A0Sheds | http://www.amd.com/us/products/embedded/processors/Pages/g-series.aspx |
| 16:07.29 | A0Sheds | http://www.amd.com/us/Documents/49282_G-Series_platform_brief.pdf |
| 16:08.27 | mnemoc | A0Sheds: I wanted opinion, not specs :p |
| 16:08.34 | mnemoc | A0Sheds: but np |
| 16:08.57 | A0Sheds | get your own :) |
| 16:09.51 | A0Sheds | that's one thing there is certainly no shortage of |
| 16:09.59 | mnemoc | i don't have the right background for make a decent own-opinion on that topic |
| 16:11.06 | mnemoc | back to coding |
| 16:16.10 | specing | "and enjoy a familiar Windows(R) 7 experience on the go" |
| 16:16.20 | specing | .. Because that is all I ever wanted... |
| 16:23.38 | CIA-158 | rhombus-tech: Peter master * rf827f317eb76 /allwinner_a10/orders/pete200.mdwn: |
| 17:23.33 | *** join/#arm-netbook sponix (~sponix@c-98-244-187-216.hsd1.ga.comcast.net) |
| 17:50.42 | hno | A0Sheds, if I get it correct then the $100 price point is board alone. You then need to add CPU, memory, ... |
| 17:50.55 | hno | and software (i.e. Windows license). |
| 17:51.01 | hno | if so inclined. |
| 17:53.50 | specing | Windows? where? who? why? |
| 17:54.28 | specing | ah |
| 17:54.44 | hno | specing, the target audience of the intel board linked above. |
| 17:54.47 | mnemoc | to enjoy the familiar experience on the go |
| 17:55.08 | specing | :( |
| 17:57.10 | hno | The Intel enty is a nice compact form factor, but I doubt it will see much traction in the consumer segment. But likely a major hit in several commercial segments. |
| 17:57.11 | mnemoc | but hopefully it will make these http://www.aliexpress.com/product-fm/539213266-AMD-APU-mini-nettop-Fusion-E450-Dual-Core-1-65GHz-1MB-cachesL2-WIFI-2G-320GB-mini-wholesalers.html go cheaper in mid-term |
| 17:59.22 | hno | mnemoc, maybe, but it's about the same target price point I think. |
| 18:00.05 | specing | An EEE PC is way cheaper |
| 18:00.33 | hno | specing, yes, but again very different. |
| 18:01.15 | specing | Ofcourse 4 EOMA A10 modules for $100 would pwn them both |
| 18:02.05 | hno | We don't know the retail price for EOMA A10 yet. |
| 18:02.55 | specing | I don't thing they will cost more than RPi A |
| 18:03.22 | mnemoc | cost to whom? :) |
| 18:04.25 | specing | what? |
| 18:04.41 | hno | mnemoc, nice note on that aliexpress offer in light of the recent licensing discussions.. "Note: If not specified, the machine does not install the system shipped. In addition, if you need to install the system, the system is cracked version." |
| 18:04.59 | *** part/#arm-netbook sponix (~sponix@c-98-244-187-216.hsd1.ga.comcast.net) |
| 18:05.16 | mnemoc | hno: doh |
| 18:06.51 | hno | mnemoc, manufacturing cost of R Pi is not known outside Broadcom. |
| 18:11.52 | hno | is of the untrusting nature and suspects Broadcom are selling those CPUs way below normal levels. |
| 18:12.23 | mnemoc | the pandaboard is sold under cost |
| 18:12.44 | hno | the R Pi is a great market stunt no doubt. |
| 18:13.13 | mnemoc | at least that's what people what some people from TI at #elinux has said |
| 18:14.09 | mnemoc | I have never expected the a10 module to be sold for less than $50... but it would be a nice surprise |
| 18:14.11 | hno | That too is a great marketing tool so I would not see it as odd. |
| 18:14.42 | hno | Yes, remains to see where the EOMA A10 ends up in price. |
| 18:15.12 | hno | still many significant unknowns. |
| 18:17.11 | hno | I would guess the volume of pandaboards produced fits in the "free samle for marketing purposes" budget in the CPU manufacturing budget. |
| 18:18.29 | hno | Compared to any "normal" market segment where those CPUs are used the Pandaboard volume is barely noticeable, but from a marketing point of view it's night and day. |
| 18:18.46 | mnemoc | yes, I believe the same |
| 18:23.50 | mnemoc | I don't remember where I read that the most basic license for a cortex-a9 is around US$5M ... |
| 18:29.56 | mnemoc | the holy wikipedia calculates it to 1.8M in 2006, and that's long before the v7 started spreading |
| 18:31.29 | destinal | hno: my point with the lapdock is lapdock includes keyboard and screen and speakers and battery and trackpad and interfaces to a computer (typically a cell phone) via micro-hdmi and micro-usb. if we made a small IO board for eoma68 that had the male hdmi and usb connectors at the same distance apart as the model of phone we were pretending to be, we would have a computer module to plug into... |
| 18:31.31 | destinal | ...the lapdock the way the phone it was designed for would |
| 18:32.07 | hno | Ah, now I get you. I thought you referred to one of those adding keyboard to a tablet. |
| 18:33.33 | hno | yes those makes a lot sense for EMOA type boards, even if EOMA isn't used at all in the setup. |
| 18:35.08 | destinal | hno: yeah you could use one of those ARM dongle computers that look like USB flash drive but then you'd need cables, for EOMA68 we could make a little handheld thing that slots right in |
| 18:35.26 | destinal | EOMACF might be a little better form factor though |
| 18:35.35 | hno | EOMA do not have HDMI. |
| 18:36.04 | destinal | hno: yeah for EOMA68 you'd need an LCD -> HDMI encodre chip on the IO board. EOMA-CF does have HDMI though |
| 18:36.18 | destinal | if it ever comes to exist |
| 18:37.14 | mnemoc | one dream at the time :) |
| 18:37.52 | hno | I would expect EMOA68 rev 1.1 to have HDMI instead of LCD interface. See earlier discussions regarding monitors & media boxes.. |
| 18:39.29 | hno | The LCD interface is basically unly useful for tablets and similar. For a monitor type setup it's just odd and unlikely to be supported by any monitor chipsets. |
| 18:40.13 | mnemoc | but the card has two sides, one on the inside for an LCD panel and one on the outside for a monitor |
| 18:40.25 | hno | while HDMI is a standard input source already supported in plenty. |
| 18:40.46 | hno | mnemoc, the point of using EOMA with a monitor is to have a slot in the monitor for adding media capabilities. |
| 18:41.11 | hno | wrongly worded. but I think you get the point. |
| 18:41.21 | mnemoc | yes |
| 18:42.10 | hno | s/with a/in a/ |
| 18:42.29 | hno | makes mre sense. |
| 18:43.09 | mnemoc | I'm not very fond to that particular use-case |
| 18:47.17 | hno | The lapdock use case destinal mentioned is pretty much the same. They are all built the same with hdmi + usb as interface. |
| 18:47.57 | destinal | mnemoc: I think we can all agree though that having to plug cables into EOMA68 is less than ideal though, the more we can get on IO board that we can just plug the card in and have it work without plugging in external cables the better |
| 18:48.28 | mnemoc | I just tend to see more value on the other set of use cases |
| 18:48.42 | destinal | mnemoc: though I understand the LCD stuff was added because one HDMI connection had a limit to how much resolution you could get off of it, basically, right? |
| 18:49.05 | mnemoc | no idea |
| 18:49.40 | destinal | and anyway we can always add encoder chip to the IO board not too expensively I think |
| 18:49.47 | hno | HDMI have limits. But it's the resolution most people use today.. |
| 18:49.58 | hno | which is less than some years ago before HDMI.. |
| 18:50.56 | mnemoc | afaik the LCD has no troubles to get 1920x1080, which is perfect more most cas |
| 18:51.01 | hno | My understanding is that LCD was selected instead of HDMI to provide very cheap tablet/laptop I/O boards. |
| 18:51.03 | mnemoc | cases* |
| 18:52.23 | hno | Quite from Wikipedia: "The maximum pixel clock rate for HDMI 1.0 was 165 MHz, which was sufficient to support 1080p and WUXGA (1920×1200) at 60 Hz. HDMI 1.3 increased that to 340 MHz, which allows for higher resolution (such as WQXGA, 2560×1600) across a single digital link.[43]" |
| 18:53.26 | hno | And then there is dual-link HDMI for double the pixelrate. |
| 18:54.49 | hno | wasn't aware HDMI 1.0 supports WUXGA.. thought it was limited to 1080. |
| 18:56.29 | hno | HDMI do have some other nice properties such as DDC to automatically detect the panel type. |
| 18:56.30 | mnemoc | the target audience of those monster display is very different imo |
| 18:56.56 | hno | yes. |
| 18:58.42 | hno | The point is that HDMI is well suitable for any targeted resolution. |
| 18:59.19 | mnemoc | but for the uses where eoma is most valuable it would make devices more expensive |
| 19:01.09 | mnemoc | for cases like that lapdock a generic hdmi+usb adapter with two cables makes far more sense imo |
| 19:01.33 | mnemoc | and then you can plug anything |
| 19:02.30 | mnemoc | including an eoma68 card |
| 19:02.32 | hno | a majort pitch of EOMA is to be able to easily switch. Using interfaces normally only used internally do not help that goal. |
| 19:03.13 | hno | Again. EOMA68 do not have HDMI. The A10 card do, but it's outside EOMA68. |
| 19:06.57 | mnemoc | allowing cards without hdmi capabilities in those inexpensive products where it's not needed |
| 19:07.11 | mnemoc | which is the vast majority |
| 19:08.39 | specing | localhost# cat mtdblock1 > mtd1.img |
| 19:08.39 | specing | mtdblock1: invalid length |
| 19:08.49 | specing | <3>[14183.230494] msm_nand_read_oob: unsupported ops->len, 512 |
| 19:08.49 | specing | <3>[14183.230624] end_request: I/O error, dev mtdblock1, sector 0 |
| 19:08.49 | specing | <3>[14183.235746] Buffer I/O error on device mtdblock1, logical block 0 |
| 19:08.50 | mnemoc | specing: use dd |
| 19:08.53 | specing | holy cow? |
| 19:09.17 | specing | dd if=mtdblock1 of=mtd.img |
| 19:09.17 | specing | mtdblock1: read error: I/O error |
| 19:09.17 | specing | 0+0 records in |
| 19:09.17 | specing | 0+0 records out |
| 19:09.18 | specing | 0 bytes transferred in 0.012 secs (0 bytes/sec) |
| 19:09.25 | mnemoc | are you backing up the sd card in the sd card? |
| 19:09.25 | CIA-158 | rhombus-tech: Evandro master * rb2e5ead92c60 /allwinner_a10/orders/EvandroJr.mdwn: |
| 19:09.52 | specing | No, Im backing up /dev/block/mtdblock1 to /dev/block/mtd.img |
| 19:10.01 | specing | <PROTECTED> |
| 19:10.29 | specing | cat mtdblock1 > /sqlite_stmt_journals/mtd1.img |
| 19:10.30 | specing | mtdblock1: invalid length |
| 19:10.43 | specing | sql.... is an another tmpfs |
| 19:10.55 | specing | What is going on? |
| 19:11.16 | mnemoc | mtdblock1 is the first partition of the SD card |
| 19:11.25 | specing | No, that is mmcblk0p1 |
| 19:11.37 | mnemoc | ok |
| 19:11.47 | specing | Im backing up NAND flash |
| 19:12.01 | rz2k | welcome to bad block world |
| 19:12.22 | mnemoc | that's /dev/nand[a-i] |
| 19:12.22 | specing | D: |
| 19:13.16 | specing | mnemoc: android kernels have block devices under /dev/block |
| 19:13.31 | specing | and there is no such thing as nand[a-z] here |
| 19:13.42 | specing | only mtdblock[0-15] |
| 19:13.49 | mnemoc | the a10's nand driver is not mtd |
| 19:13.57 | specing | This is not A10 :) |
| 19:14.08 | mnemoc | ok |
| 19:14.17 | specing | This is my partially bricked phone :S |
| 19:14.36 | *** join/#arm-netbook mpthompson (~IceChat77@c-50-131-39-81.hsd1.ca.comcast.net) |
| 19:14.39 | mnemoc | i see |
| 19:15.17 | specing | Mounting works just fine :/ |
| 19:19.41 | hno | specing, well.. mtd is different. not block based. mdtblock is an emulation layer ontop of mtd to support block based filesystems. |
| 19:19.56 | hno | what filesystem is used? |
| 19:24.42 | specing | yaffs2 |
| 19:26.14 | hno | then mtdblock is not used, only mtd. |
| 19:27.13 | specing | Well it does not boot, so I guess it is somehow... broken? |
| 19:29.42 | hno | to dump yaffss partitions you need to use nanddump to dump the nand. |
| 19:30.13 | hno | yaffs2 makes use of all bits in the nand, not only the normal data bits. |
| 19:38.09 | hno | specing, you can't access an yaffs2 partition using mtdblock. The two are not compatible. |
| 19:48.34 | specing | D: |
| 19:48.42 | specing | Well |
| 19:48.58 | specing | But the first mtd block should be the boot.img |
| 19:48.58 | hno | well? |
| 19:49.33 | hno | why do you think it's an mtdblock? |
| 19:49.40 | specing | hmmm |
| 19:49.59 | specing | mtdblock0 can be yaffs2 mounted, mtdblock1 cannot |
| 19:50.17 | specing | err, it can |
| 19:50.21 | specing | But it is empty |
| 19:50.23 | specing | I wonder why |
| 19:50.40 | hno | mtdblock is for emulating a block device making NAND suitable for read-only access by a normal block based filesystem. |
| 19:51.06 | hno | mounting anything non-jffs2 as a jffs2 filesystem erases the flash partition. |
| 19:51.23 | mnemoc | nice feature |
| 19:51.49 | hno | automatic mkfs so to say. |
| 19:52.25 | mnemoc | i assumed they all checked the magic signature before even trying to do anything |
| 19:52.27 | specing | <6>[ 1.867858] Found a supported NAND device |
| 19:52.27 | specing | <6>[ 1.871834] NAND Id : 0x5590bc2c |
| 19:52.27 | specing | <6>[ 1.875144] Buswidth : 16 Bits |
| 19:52.27 | specing | <6>[ 1.878258] Density : 512 MByte |
| 19:52.27 | specing | <6>[ 1.881469] Pagesize : 2048 Bytes |
| 19:52.29 | specing | <6>[ 1.884779] Erasesize: 131072 Bytes |
| 19:52.32 | specing | <6>[ 1.888239] Oobsize : 64 Bytes |
| 19:52.34 | specing | <6>[ 1.891366] CFG0 Init : 0xa85408c0 |
| 19:52.37 | specing | <6>[ 1.894936] CFG1 Init : 0x0004745e |
| 19:52.39 | specing | <6>[ 1.898483] ECCBUFCFG : 0x00000203 |
| 19:52.42 | specing | <5>[ 1.902056] Creating 15 MTD partitions on "msm_nand": |
| 19:52.44 | specing | <5>[ 1.907099] 0x0000045a0000-0x000004b60000 : "boot" |
| 19:52.47 | specing | <5>[ 1.915601] 0x000004b60000-0x000008760000 : "cache" |
| 19:52.49 | specing | <5>[ 1.947944] 0x000008760000-0x000008c60000 : "recovery" |
| 19:52.56 | specing | I guess I nuked them, somehow... |
| 19:53.02 | hno | specing, use a paste site such as fpaste. |
| 19:56.25 | hno | if you mounted them as yaffs2 without them actually being yaffs2 then consider them nuked. |
| 19:57.59 | mnemoc | specing: can't you reflash to factory state? |
| 19:58.31 | specing | I guess I can, I have an update.zip from the 'net |
| 19:58.54 | specing | And Im booting from a modified boot.img from there right now |
| 19:59.23 | mnemoc | so, what are you waiting for? :) |
| 19:59.38 | specing | Well I just wanted to see what was wrong |
| 20:00.12 | mnemoc | partitions nuked, game over. insert coin^Wupdate.zip |
| 20:02.39 | specing | Why is it even in a zip? I'd expect it to be in a tar since zip doesent support (AFAIK) unix permission bits |
| 20:02.57 | specing | Or does it? |
| 20:03.26 | mnemoc | inside the zip there are image files and plain text |
| 20:03.36 | mnemoc | nothing complex |
| 20:03.52 | mnemoc | apk files are also .zip |
| 20:04.09 | specing | and executables |
| 20:04.28 | specing | update.zip is boot.img + systemfs + custpackfs |
| 20:05.02 | specing | Took me half an hour to get zsh working on that strange setup! |
| 20:15.19 | hno | specing, all android is strange.. |
| 20:18.57 | mnemoc | all those formats are modelled as extensions of .jar ... probably very natural choice for java people |
| 20:19.40 | specing | D: |
| 20:20.37 | specing | Its like 9/10 of all common unix utilities are missing |
| 20:24.24 | mnemoc | linaro's android tree comes with busybox by default |
| 20:24.43 | mnemoc | but G doesn't want any other bit of GPL beside the kernel in there |
| 20:25.04 | mnemoc | to remain "frienly" with the "industry" |
| 20:26.19 | specing | Dont all androids come with busybox? |
| 20:26.24 | specing | Mine sure did |
| 20:26.36 | mnemoc | nope |
| 20:26.46 | specing | both the A10 tab and phone |
| 20:27.00 | mnemoc | lucky you ;-) |
| 20:27.27 | mnemoc | that's usually because they didn't care to clean their engineering system before sending it to production |
| 20:29.23 | specing | I believe that was the case with the A10, but my phone is of french design (alcatel) |
| 20:29.47 | specing | Im not sure about my archos tablet, but I think it also came with busybox |
| 20:30.25 | mnemoc | most big-brand phones I know don't even come with `su` |
| 20:31.14 | specing | My phone doesen't have su, same with archos |
| 20:31.17 | specing | the A10 does |
| 20:32.17 | specing | Im baffled by the strange init.rc syntax |
| 20:32.58 | mnemoc | android by default comes with a su binary, removing it is part of the securing phase |
| 20:33.07 | mnemoc | same as disabling `adb root` |
| 20:34.15 | mnemoc | very annoying :( |
| 20:34.17 | specing | Doesen't matter, have psneuter |
| 20:34.19 | specing | :) |
| 20:34.59 | mnemoc | exploit? |
| 20:35.21 | specing | yes |
| 20:35.35 | specing | Not exactly sure what is does, but it works |
| 20:36.15 | mnemoc | https://github.com/tmzt/g2root-kmod/blob/master/scotty2/psneuter/psneuter.c <--- read the comment on top ;-) |
| 20:42.03 | specing | Im wondering why it is not booting |
| 20:42.26 | specing | It can't be that its just the boot parition werecked |
| 20:42.46 | specing | both system and custpack are exact matches with their backups |
| 20:44.43 | mnemoc | reflash it and see if it boot :) |
| 20:58.03 | specing | Nah, that would mean that I would lose the fastboot interface (until I nuke that partition again) |
| 21:06.34 | CIA-158 | rhombus-tech: Pawel master * r99c0f83e6929 /allwinner_a10/orders/sonsky.mdwn: |
| 21:07.10 | hno | specing, you have some recovery mechanism if boot partition is lost? |
| 21:09.10 | specing | fastboot... |
| 21:09.22 | specing | It is already lost |
| 21:09.47 | specing | The update.zip kernel's config.gz doesen't match my proc backups |
| 21:09.50 | specing | D: |
| 21:18.58 | *** join/#arm-netbook hp_|2 (~kvirc@118-168-206-95.dynamic.hinet.net) |
| 21:19.15 | specing | This phone might be better than I thought |
| 21:19.36 | specing | There are traces of a real serial port in dmesg |
| 21:40.26 | *** join/#arm-netbook mpthompson (~IceChat77@c-50-131-39-81.hsd1.ca.comcast.net) |
| 21:43.39 | A0Sheds | imx6 delayed |
| 21:50.14 | hno | specing, the SoC almost certainly have an UART. But it's another story if it's connected. |
| 21:50.54 | hno | the A10 have 8 UARTs I think. 4 are usable from Linux by default. |
| 21:52.41 | hno | normallly 2-3 are used in a phone. debug UART, GPS UART, and sometimes something more. |
| 21:53.27 | hno | specing, any pads under the battery? That is a common location for debug UARTs etc.. |
| 21:54.08 | hno | with a debug jig that provides pover and have spring pins that connect to those pads. |
| 21:54.23 | hno | s/pov/pow/ |
| 21:55.07 | hno | specing, if you have fastboot then the bootloader is intact at least. But be warned that that as well is most likely in the nand. |
| 21:59.39 | *** join/#arm-netbook mikey_w (~mike@c-71-63-115-202.hsd1.va.comcast.net) |
| 21:59.46 | *** join/#arm-netbook mike_ (~mike@c-71-63-115-202.hsd1.va.comcast.net) |
| 23:02.02 | CIA-158 | rhombus-tech: Damon master * r3d7743c14a06 /allwinner_a10/orders/nomade30.mdwn: |