| 02:59.47 | *** join/#arm-netbook Gamayun_ (~Gamayun@host-92-0-150-123.as43234.net) |
| 03:22.12 | *** join/#arm-netbook fitzsim` (~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f) |
| 03:23.54 | *** join/#arm-netbook yang_ (yang@irs.si) |
| 03:23.57 | *** join/#arm-netbook yang_ (yang@freenode/sponsor/fsf.member.yang) |
| 03:29.06 | *** join/#arm-netbook dyoung (dyoung@nasadmin/dyoung) |
| 04:59.21 | *** join/#arm-netbook ohama (ohama@cicolina.org) |
| 05:22.06 | *** join/#arm-netbook mm|Bot (~modelmoti@unaffiliated/modelmotion) |
| 07:09.09 | *** join/#arm-netbook Putti (~Putti@unaffiliated/putti) |
| 10:05.56 | *** join/#arm-netbook jonasbits (~quassel@94-245-54-172.customer.t3.se) |
| 10:16.03 | *** join/#arm-netbook Putti (~Putti@unaffiliated/putti) |
| 11:17.15 | *** join/#arm-netbook stamina (~stamina@232-056-128-083.dynamic.caiway.nl) |
| 11:19.23 | *** join/#arm-netbook SirCmpwn (sircmpwn@irc.sircmpwn.com) |
| 11:51.14 | *** join/#arm-netbook Putti (~Putti@unaffiliated/putti) |
| 11:52.04 | *** join/#arm-netbook Gamayun (~Gamayun@host-92-0-150-123.as43234.net) |
| 12:03.31 | *** join/#arm-netbook mm|Bot (~modelmoti@c-73-1-201-113.hsd1.fl.comcast.net) |
| 12:03.45 | *** join/#arm-netbook mm|Bot (~modelmoti@unaffiliated/modelmotion) |
| 12:13.50 | *** join/#arm-netbook ganbold (~ganbold@173.244.215.173) |
| 12:16.16 | *** join/#arm-netbook Tsutsu (~Tsutsukak@163.172.151.191) |
| 12:38.31 | *** part/#arm-netbook Tsutsu (~Tsutsukak@163.172.151.191) |
| 13:54.36 | *** join/#arm-netbook Putti (~Putti@unaffiliated/putti) |
| 14:43.45 | *** join/#arm-netbook hssa (~Amug@50.49.212.151) |
| 15:01.15 | *** join/#arm-netbook OmegaPhil (~kvirc@88.97.77.255) |
| 15:01.15 | *** join/#arm-netbook OmegaPhil (~kvirc@fsf/member/OmegaPhil) |
| 15:04.34 | *** join/#arm-netbook _whitelogger (~whitelogg@uruz.whitequark.org) |
| 15:29.35 | *** join/#arm-netbook hssa (~Amug@50.49.212.151) |
| 15:30.19 | SPG | Luke Leighton master 6f68521 source whitepapers/ecocomputing_07sep2015.mdwn update mbit to gbit * http://source.rhombus-tech.net/?p=source.git;a=commitdiff;h=6f68521 |
| 15:45.38 | ericxdu | Oh hi lkcl and thanks for the welcome |
| 17:15.10 | *** join/#arm-netbook OmegaPhil (~kvirc@88.97.77.255) |
| 17:15.11 | *** join/#arm-netbook OmegaPhil (~kvirc@fsf/member/OmegaPhil) |
| 17:16.20 | *** join/#arm-netbook isacdaavid (~isaac@187.232.105.34) |
| 18:25.35 | mozzwald | lkcl: is there a pinout or schematic for the cpu card avail? i can't seem to find it if it's available. I looked here but it seems to be all datasheets http://hands.com/~lkcl/eoma/allwinner/ |
| 18:44.52 | *** join/#arm-netbook desttinghim (~desttingh@50.50.159.179) |
| 18:51.23 | *** join/#arm-netbook Kraln (~kraln@69.169.90.240) |
| 19:11.09 | oh2ftg | mozzwald: card pinnout http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68 |
| 19:11.20 | oh2ftg | scroll down to "Table of EOMA-68 pinouts" |
| 19:14.39 | oh2ftg | the rhombus-tech site is really hard to navigate, but I did find schematic links there, somewhere |
| 19:15.08 | oh2ftg | apparently this git repo has the schematics http://git.rhombus-tech.net/eoma |
| 19:15.22 | oh2ftg | mentionded here http://rhombus-tech.net/allwinner_a10/pcb/ |
| 19:15.48 | oh2ftg | but the page refers to allwinner a10, when according to my understanding, the current card as a20 |
| 19:35.27 | *** join/#arm-netbook curtis22 (~curtis@63.135.2.175) |
| 19:50.54 | desttinghim | I think I've seen it mentioned a couple times where the A20 is a drop in replacement for the A10 |
| 19:51.14 | desttinghim | Take that with a grain of salt though |
| 20:34.02 | *** join/#arm-netbook SirCmpwn (sircmpwn@irc.sircmpwn.com) |
| 20:37.04 | *** join/#arm-netbook arkimedes (~arkimedes@199.58.81.144) |
| 20:47.55 | mozzwald | oh2ftg: thanks. I knew of the elinux pinout. was looking for the pcb pinout to see alternate functions of the cpu pins on the eoma interface (and internal header) |
| 20:48.54 | oh2ftg | no idea about internal headers |
| 20:49.05 | mozzwald | the sitemap at rhombus-tech site seems to be the way to find stuff. I didn't think to look at the a10 board |
| 20:49.15 | oh2ftg | and as the card is eoma68 compliant, the pins should match the standard |
| 20:49.25 | oh2ftg | mozzwald: me neither, I used the site map |
| 20:49.26 | mozzwald | which I think is same/similar to the a20 as desttinghim says |
| 20:50.01 | arkimedes | hey lkcl congrats on the funding completion!! |
| 20:50.10 | arkimedes | sorry i havent been able to work on the site yet got super swamped with stuff |
| 20:50.14 | *** join/#arm-netbook stamina (~stamina@232-056-128-083.dynamic.caiway.nl) |
| 20:50.37 | mozzwald | yeah, pins on eoma should match the standard. I was just curious what other functions were available on them |
| 20:51.11 | mozzwald | and I think there is an internal header on the cpu card |
| 20:53.28 | oh2ftg | well the other functions available are the one's mentioned in the eoma68 standard |
| 20:55.42 | mozzwald | typically, cpu's have multiple functions on 1 pin. so, if one wanted to not use usb on a set of pins, you could use them as regular gpio or whatever else the cpu provides on that pin |
| 21:05.15 | oh2ftg | maybe, but with that software the card would become incompliant to eoma68 and noncompatible with all/most hardware made for eoma68 use |
| 21:08.56 | mozzwald | i understand, and agree :) I'm just curious |
| 21:27.52 | mozzwald | anyways, looks like the a10 schematics/layout are for the old eoma spec. I see sata and ethernet in it |
| 21:34.06 | arossdotme | mozzwald, there are no optional pins, use a arduino-like thingy for gpio :) |
| 21:34.57 | arossdotme | i use the sitemap my self to get around. the site does need work, i belive your welcome to try improve it, login and start editing :) |
| 21:35.38 | arossdotme | so then the question is what to make the menu structure into ? heh |
| 21:36.17 | arossdotme | decisions, ponders, debates, trials |
| 21:36.24 | arossdotme | etc |
| 21:47.10 | mozzwald | arossdotme: i fully understand what the specifications of eoma68 require :) |
| 21:49.50 | *** join/#arm-netbook hssa (~Amug@50.49.212.151) |
| 21:52.22 | mozzwald | my point is, i should be able to work outside that spec in the comfort of my own home. this is free/libre project, yes? |
| 21:53.43 | hssa | pretty sure it is free and libre. |
| 21:53.51 | hssa | who are you talking to |
| 21:53.54 | hssa | ? |
| 21:54.09 | hssa | I am curious if the main dev is here |
| 21:54.13 | hssa | thats why i ask |
| 21:58.03 | mozzwald | just making a point i guess |
| 21:58.35 | hssa | do you use trisquel forums at all? |
| 21:59.00 | mozzwald | i'm just curious to see the schematics if available. they may not be |
| 21:59.03 | hssa | I believe he has uploaded some of the source code to the design already |
| 21:59.14 | hssa | Rhombus tech maybe has it |
| 21:59.19 | hssa | on that website |
| 21:59.37 | mozzwald | i havent checked trisquel. i'll check it out. |
| 21:59.39 | hssa | I would have to look it up again but the people are trisquel.info said they |
| 21:59.49 | hssa | that Luke uploaded the schematics |
| 21:59.50 | mozzwald | cant find it in the rhombustech site |
| 21:59.54 | hssa | hmm |
| 22:00.06 | hssa | well if you want i can look up your question |
| 22:00.11 | hssa | Since you seem curious |
| 22:00.27 | hssa | I will ask that forum |
| 22:00.32 | hssa | you use linux right? |
| 22:00.39 | hssa | gnu/linux to be more accurate |
| 22:00.43 | mozzwald | yes |
| 22:00.51 | hssa | okay |
| 22:01.10 | mozzwald | thanks |
| 22:01.38 | hssa | oh by the way |
| 22:02.02 | hssa | I am going to make a thread about it on trisquel's forums feel free to look at the replies it gets okay? |
| 22:02.07 | hssa | trisquel.info is the website |
| 22:02.16 | hssa | go to the forums and calmstorm is my username |
| 22:04.26 | hssa | okay I made the post |
| 22:04.40 | hssa | I will no doubt return in the future |
| 22:04.53 | hssa | So if you see me ask me to look it up if you don't remember to do so yourself |
| 22:04.57 | hssa | gtg |
| 22:05.03 | mozzwald | awesome, i'll check it out. thx |
| 22:25.58 | *** join/#arm-netbook mm|Vamp (~modelmoti@c-73-1-201-113.hsd1.fl.comcast.net) |
| 22:33.36 | *** join/#arm-netbook mattl (sid14229@gnu/mattl) |
| 22:40.00 | *** join/#arm-netbook curtis22 (~curtis@63.135.2.175) |
| 22:55.29 | lkcl | arkimedes: thxman.... just got a looot of work to do now :) |
| 22:56.46 | lkcl | mozzwald: there is an internal header... it's an FPC20 i think... i'm not going to be putting it on by default |
| 22:57.20 | mozzwald | ah, sweet |
| 22:57.51 | lkcl | mozzwald: http://lists.phcomp.co.uk/pipermail/arm-netbook/2016-August/011644.html |
| 22:57.57 | lkcl | mozzwald: track the links there. |
| 22:58.43 | lkcl | mozzwald: but please, if you're thinking of using any EOMA68 computer card for "non" EOMA68 features... please don't. |
| 22:59.43 | mozzwald | like i said, "in the comfort of my own home." I wouldn't release a real product that was non compliant |
| 23:00.00 | mozzwald | thanks for the links |
| 23:01.10 | lkcl | mozzwald: it's not so much that - it's that you'll end up developing something that, when *you* come to upgrading, you have to start again entirely from scratch... because you used a feature of the A10 that's not part of EOMA68. |
| 23:02.16 | lkcl | mozzwald: just bear that in mind. for example the A64 has a totally different pinouts... do the multiplexed functions of the A20 match even the *slightest* bit with those of the A64? absolutely none of them do! |
| 23:02.48 | lkcl | mozzwald: which means that you relegate the EOMA68-A20 to "just another SBC to be thrown into landfill" |
| 23:03.41 | lkcl | if that makes any sense. |
| 23:03.44 | mozzwald | I understand the concerns :) I don't even know if there's anything I'd use. |
| 23:04.47 | mozzwald | and it makes sense, yes. it's still anyones choice to do what they want with it |
| 23:07.54 | lkcl | mozzwald: correct.... it is.... but i'm not allowing people to claim it's "compatible with the EOMA68 standard" if they use alternative functions. |
| 23:08.36 | lkcl | mozzwald: that's *really* important because if people start doing that, they're in effect CLAIMING that they have authorisation to EXTEND the EOMA68 standard.... which they most certainly do not. |
| 23:08.57 | lkcl | mozzwald: thus they would be bringing the standard into disrepute.... and that's where i have to put my foot down. |
| 23:11.44 | mozzwald | lkcl: right. no one should claim to have an eoma68 compliant device if it doesn't meet the spec. |
| 23:12.48 | lkcl | mozzwald: correct. |
| 23:13.05 | lkcl | mozzwald: so with that proviso in mind.... feel free :) |
| 23:14.23 | mozzwald | my interest is for personal use. and again, I dunno if I will even want to use the multiplexed functions, or have a need. I just like to know my options :D |
| 23:19.35 | *** join/#arm-netbook m6lpi (sid19617@gateway/web/irccloud.com/x-ikvogmtkomedzgyp) |
| 23:22.56 | lkcl | mozzwald: push the boundaries. so... now you know :) |