From jim at smt.no-ip.co.uk Mon Apr 2 21:21:49 2018 From: jim at smt.no-ip.co.uk (jim) Date: Mon, 02 Apr 2018 21:21:49 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams Message-ID: <54ece8ee3b53731dd4583b073d473fe8@localhost> Hi, I'm out on a limb with Allwinner R40 circuit diagram. I want to make open source KiCAD Linux board(s). This time I got more funding to finish the project compared to the A10/A20 version tried when EOMA was being prototyped :) https://hellosemi.com/KiCAD_Linux_Boards.html I only find the BPi version so far. Anyone know of any others open sourced boards that I could learn from? Regards, Joe From eaterjolly at gmail.com Sat Apr 7 01:35:53 2018 From: eaterjolly at gmail.com (Jean Flamelle) Date: Fri, 6 Apr 2018 20:35:53 -0400 Subject: [Arm-netbook] Computer without Entropy Message-ID: Is it possible to take RISC design to an extreme and design a core without any practical vectors for entropy based on timekeeping? Something like lambda calculus on a chip, except differentiating multiple output devices not just a theoretical "tape". Of course damage will always create some entropy, but not the kind which can be harnessed in anyway relevant to the current imagination. From maillist_arm-netbook at aross.me Sat Apr 7 21:50:34 2018 From: maillist_arm-netbook at aross.me (Alexander Ross) Date: Sat, 7 Apr 2018 21:50:34 +0100 Subject: [Arm-netbook] OT: verify.sandisk.cn is working? Message-ID: <6470ff53-0bb1-497c-cf9f-fffad71f7f38@aross.me> Got sd card from china, write speeds are 5mb/s (1gb files i think) using f3 to test capacity. Anyway wanted to verify its genuine but http://verify.sandisk.cn/ doesn’t load for me, not even when using tor. i can access http://sandisk.cn/ If someone whos not too busy. Fancy seeing if it works in china? Else anyone got a recommendation for a no-fee proxy into china? Verify number: 888285238468559181 Thanks From lkcl at lkcl.net Sat Apr 7 22:07:06 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Sat, 7 Apr 2018 22:07:06 +0100 Subject: [Arm-netbook] OT: verify.sandisk.cn is working? In-Reply-To: <6470ff53-0bb1-497c-cf9f-fffad71f7f38@aross.me> References: <6470ff53-0bb1-497c-cf9f-fffad71f7f38@aross.me> Message-ID: --- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Sat, Apr 7, 2018 at 9:50 PM, Alexander Ross wrote: > Got sd card from china, write speeds are 5mb/s (1gb files i think) > using f3 to test capacity. > > Anyway wanted to verify its genuine but http://verify.sandisk.cn/ > doesn’t load for me, not even when using tor. i can access > http://sandisk.cn/ https://verify.sandisk.cn does actually respond (with an invalid certificate) so there's definitely something there. telnet to port 80 and type "HEAD HTTP/1.1 /" or something like that. l. From research at enemygadgets.com Mon Apr 9 15:34:44 2018 From: research at enemygadgets.com (joem) Date: Mon, 09 Apr 2018 15:34:44 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams Message-ID: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> 7th page uploaded in KiCAD https://hellosemi.com/KiCAD_Linux_Boards.html (Still only find the BPi version so far) Thinking first board will be a minimalist square board with SoC 2GB DRAM serial uSD HDMI PMIC SATA USB flash just to get it to boot. From lkcl at lkcl.net Mon Apr 9 18:17:48 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Mon, 9 Apr 2018 18:17:48 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams In-Reply-To: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> References: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> Message-ID: --- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Mon, Apr 9, 2018 at 3:34 PM, joem wrote: > 7th page uploaded in KiCAD > > https://hellosemi.com/KiCAD_Linux_Boards.html fantastic! > (Still only find the BPi version so far) > > Thinking first board will be a minimalist square board with SoC 2GB DRAM > serial uSD HDMI PMIC SATA USB flash just to get it to boot. sounds eminently sensible. l. From research at enemygadgets.com Thu Apr 12 00:30:20 2018 From: research at enemygadgets.com (joem) Date: Thu, 12 Apr 2018 00:30:20 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams In-Reply-To: References: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> Message-ID: All 11 page KiCAD conversion complete and uploaded. Now moving to layout - done up Allwinner R40 BGA and 8GB eMMC BGA footprints. https://hellosemi.com/KiCAD_Linux_Boards.html >> Thinking first board will be a minimalist square board with SoC 2GB DRAM >> serial uSD HDMI PMIC SATA USB flash just to get it to boot. > > sounds eminently sensible. From lkcl at lkcl.net Thu Apr 12 00:41:10 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Thu, 12 Apr 2018 00:41:10 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams In-Reply-To: References: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> Message-ID: On Thu, Apr 12, 2018 at 12:30 AM, joem wrote: > All 11 page KiCAD conversion complete and uploaded. > Now moving to layout - done up Allwinner R40 BGA and 8GB eMMC BGA > footprints. > > https://hellosemi.com/KiCAD_Linux_Boards.html very cool! From eaterjolly at gmail.com Thu Apr 12 03:20:50 2018 From: eaterjolly at gmail.com (Jean Flamelle) Date: Wed, 11 Apr 2018 22:20:50 -0400 Subject: [Arm-netbook] OT: China 12 LED RGBW Par Firmware? In-Reply-To: <18465bcf-20ae-ed5d-800c-37edf90130ff@aross.me> References: <18465bcf-20ae-ed5d-800c-37edf90130ff@aross.me> Message-ID: A month and no response, looks like you'll need to break out a logic analyzer xP From research at enemygadgets.com Fri Apr 13 00:08:52 2018 From: research at enemygadgets.com (joem) Date: Fri, 13 Apr 2018 00:08:52 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams In-Reply-To: References: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> Message-ID: <46a27494de67de180d5a8cd275611e85@enemygadgets.com> Now finished footprints for all essential items - Ethernet, SMD version of SATA, uSD card, DDR, HDMI, AP6212 WIFI, AXP221s PMIC, eMMC, R40 CPU. With these anyone should be able to lay out their own boards. >> All 11 page KiCAD conversion complete and uploaded. >> Now moving to layout - done up Allwinner R40 BGA and 8GB eMMC BGA >> footprints. >> >> https://hellosemi.com/KiCAD_Linux_Boards.html > > very cool! From lkcl at lkcl.net Fri Apr 13 00:46:36 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Fri, 13 Apr 2018 00:46:36 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams In-Reply-To: <46a27494de67de180d5a8cd275611e85@enemygadgets.com> References: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> <46a27494de67de180d5a8cd275611e85@enemygadgets.com> Message-ID: On Fri, Apr 13, 2018 at 12:08 AM, joem wrote: > Now finished footprints for all essential items - Ethernet, SMD version > of SATA, uSD card, DDR, HDMI, AP6212 WIFI, AXP221s PMIC, eMMC, R40 CPU. > With these anyone should be able to lay out their own boards. superb. i might point someone i know at these, he may be interested to use them. l. From research at enemygadgets.com Mon Apr 16 18:50:59 2018 From: research at enemygadgets.com (joem) Date: Mon, 16 Apr 2018 18:50:59 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams In-Reply-To: References: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> <46a27494de67de180d5a8cd275611e85@enemygadgets.com> Message-ID: On 2018-04-13 00:46, Luke Kenneth Casson Leighton wrote: > superb. i might point someone i know at these, he may be interested > to use them. You are welcome :) Now I customize the design into a new minimalist R40 server board: https://www.hellosemi.com/KiCAD_Server_Board.html This board has 2GB RAM, gbit ethernet, SATA, camera, MIPI display, HDMI, uSD, 8GB flash, USB OTG, USB 2.0 x 2. Removed are wifi/bluetooth, audio, mic, Pi connector, IR module. The 8GB flash required a lot of rework as the BGA pinouts were incorrect in the original drawing. Also I had duplicate annotation and missing annotations in my previous KiCAD. Added more footprints where they did not exist from KiCAD libraries. All footprints were copied to local relative directory because switching between different PCs is a total pain at this moment with KiCAD. After all that work, the netlist import works without errors, and viewing 3D works without errors :) Anyone can lay it out now. I'm guessing this PCB will come out with a BOM cost less than $20. For some reason Allwinner R40 SATA read seems fast but write is very sloooow. Anyone know? From lkcl at lkcl.net Mon Apr 16 19:01:43 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Mon, 16 Apr 2018 19:01:43 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams In-Reply-To: References: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> <46a27494de67de180d5a8cd275611e85@enemygadgets.com> Message-ID: --- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Mon, Apr 16, 2018 at 6:50 PM, joem wrote: > On 2018-04-13 00:46, Luke Kenneth Casson Leighton wrote: > >> superb. i might point someone i know at these, he may be interested >> to use them. > > You are welcome :) > > Now I customize the design into a new minimalist R40 server board: > https://www.hellosemi.com/KiCAD_Server_Board.html > > This board has 2GB RAM, gbit ethernet, SATA, camera, MIPI display, HDMI, is ir 4x DDR3 x8? those are getting stupidly hard to get hold of however i found a company in taiwan that can make some. l. From research at enemygadgets.com Mon Apr 16 19:32:49 2018 From: research at enemygadgets.com (joem) Date: Mon, 16 Apr 2018 19:32:49 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams In-Reply-To: References: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> <46a27494de67de180d5a8cd275611e85@enemygadgets.com> Message-ID: <0e488485f580c549d7d9acee6128fe84@enemygadgets.com> > is ir 4x DDR3 x8? those are getting stupidly hard to get hold of > however i found a company in taiwan that can make some. SK Hynix H5TQ4G83AFR = 512M x 8 I think this week layout finish and I send it off to be made. If the RAM cannot be sourced, then get it laid out with new RAM in 'no time' because there is KiCAD drawings available. All these improvements to KiCAD has made it thunderingly fast. A lot of the work actually got done in text editor and spread sheet csv files believe it or not ;) That is because the entire data is in text files instead of binary files. I want to add a $1 STduino chip to gain control of the server at pre-boot stage and post-boot so when it goes into an array, I can talk to the board through RS232 link to the stduino to tell it to reboot the board, or shut it down in a server array without adding any more complexity to the board. I might do that before sending it off to get it made. Adds 1 to 2 days delay because I got all that in KiCAD already :) From lkcl at lkcl.net Mon Apr 16 19:39:24 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Mon, 16 Apr 2018 19:39:24 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams In-Reply-To: <0e488485f580c549d7d9acee6128fe84@enemygadgets.com> References: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> <46a27494de67de180d5a8cd275611e85@enemygadgets.com> <0e488485f580c549d7d9acee6128fe84@enemygadgets.com> Message-ID: On Mon, Apr 16, 2018 at 7:32 PM, joem wrote: >> is ir 4x DDR3 x8? those are getting stupidly hard to get hold of >> however i found a company in taiwan that can make some. > > SK Hynix H5TQ4G83AFR = 512M x 8 27 RMB that means EIGHTEEN dollars just in RAM ICs. that's if you can get hold of them. > I want to add a $1 STduino chip to gain control of the server > at pre-boot stage and post-boot so when it goes into an array, STM8S003 is ridiculously cheap and really awesome. STM32F030 is also likewise cheap. l. From research at enemygadgets.com Mon Apr 16 20:04:29 2018 From: research at enemygadgets.com (joem) Date: Mon, 16 Apr 2018 20:04:29 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams In-Reply-To: References: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> <46a27494de67de180d5a8cd275611e85@enemygadgets.com> <0e488485f580c549d7d9acee6128fe84@enemygadgets.com> Message-ID: <73fc7ddc31ce9ec2203792bf5eb66730@enemygadgets.com> On 2018-04-16 19:39, Luke Kenneth Casson Leighton wrote: > On Mon, Apr 16, 2018 at 7:32 PM, joem wrote: is ir 4x DDR3 x8? those are getting stupidly hard to get hold of > however i found a company in taiwan that can make some. > SK Hynix H5TQ4G83AFR = 512M x 8 27 RMB that means EIGHTEEN dollars just in RAM ICs. that's if you can get hold of them. First get it to boot, then ditch for cheaper RAM - someone selling for $14 (probably fake). Thanks for head up. >> I want to add a $1 STduino chip to gain control of the server >> at pre-boot stage and post-boot so when it goes into an array, > > STM8S003 is ridiculously cheap and really awesome. STM32F030 is also > likewise cheap. STM32F103C8T6 or GD32F103C8T6 - has USB so skip having to buy a separate USB serial Twitter handle - https://twitter.com/HelloHypercube From lkcl at lkcl.net Mon Apr 16 22:09:08 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Mon, 16 Apr 2018 22:09:08 +0100 Subject: [Arm-netbook] Open source Allwinner R40 circuit diagrams In-Reply-To: <73fc7ddc31ce9ec2203792bf5eb66730@enemygadgets.com> References: <4cc0fbfcea487755ce74780e71b44226@enemygadgets.com> <46a27494de67de180d5a8cd275611e85@enemygadgets.com> <0e488485f580c549d7d9acee6128fe84@enemygadgets.com> <73fc7ddc31ce9ec2203792bf5eb66730@enemygadgets.com> Message-ID: On Mon, Apr 16, 2018 at 8:04 PM, joem wrote: > On 2018-04-16 19:39, Luke Kenneth Casson Leighton wrote: > >> On Mon, Apr 16, 2018 at 7:32 PM, joem wrote: is ir 4x DDR3 x8? those are getting stupidly hard to get hold of >> however i found a company in taiwan that can make some. >> SK Hynix H5TQ4G83AFR = 512M x 8 > > 27 RMB that means EIGHTEEN dollars just in RAM ICs. that's if you > can get hold of them. > > First get it to boot, then ditch for cheaper RAM - someone selling for > $14 > (probably fake). posssibbllyyy.... you might get lucky, but have someone actually from china buy them so they have "legal recourse". > Thanks for head up. no problem. >>> I want to add a $1 STduino chip to gain control of the server >>> at pre-boot stage and post-boot so when it goes into an array, >> >> STM8S003 is ridiculously cheap and really awesome. STM32F030 is also >> likewise cheap. > > STM32F103C8T6 or GD32F103C8T6 - has USB so skip having to buy a separate > USB serial oh of course. then STM32F070 / 072 - they're cheaper than the 103. i think l. From richard.wilbur at gmail.com Tue Apr 17 21:54:29 2018 From: richard.wilbur at gmail.com (Richard Wilbur) Date: Tue, 17 Apr 2018 14:54:29 -0600 Subject: [Arm-netbook] devicetree and testing Message-ID: On Apr 16, 2018, at 22:04, Luke Kenneth Casson Leighton wrote: On Tue, Apr 17, 2018 at 4:53 AM, Richard Wilbur wrote: I am working on the devicetree for the microdesktop v1.7 and the DS113 v2.7.5 as it sounds like that is the natural prerequisite to auto-configuration and more-automated testing. awesome. remember though that testing will be done with 3.4.104+ as it's where 100% of the functionality is present. If I'm understanding you correctly the 3.4.104 kernel is the most recent kernel to have free support for all the promised functionality of the DS-113, but lacks devicetree support to make that functionality autoconfigurable? That is a beastly spot to be in! In that case I'll make the manual tables from which we can initially code up some tests by using the gpio driver and later write up the devicetree. So, sorry for being a bit thick headed, it just dawned on me what our priorities have to be and why: 1. Hack together some tests under 3.4.104 that we can run on the extant drivers. 2. Work on getting extant A20 drivers mainlined in the linux kernel. 3. Create devicetree for DS113 v2.7.4 and v2.7.5, … (all extant versions of DS113 and microdesktop case). 4. Work on getting devicetree with add/remove overlay support mainlined in the linux kernel (and u-boot?). --Richard From lkcl at lkcl.net Tue Apr 17 22:47:19 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Tue, 17 Apr 2018 22:47:19 +0100 Subject: [Arm-netbook] devicetree and testing In-Reply-To: References: Message-ID: --- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Tue, Apr 17, 2018 at 9:54 PM, Richard Wilbur wrote: > On Apr 16, 2018, at 22:04, Luke Kenneth Casson Leighton > wrote: > On Tue, Apr 17, 2018 at 4:53 AM, Richard Wilbur > wrote: > I am working on the devicetree for the microdesktop v1.7 and the DS113 > v2.7.5 as it sounds like that is the natural prerequisite to > auto-configuration and more-automated testing. > > awesome. remember though that testing will be done with 3.4.104+ as it's > where 100% of the functionality is present. > > If I'm understanding you correctly the 3.4.104 kernel is the most recent > kernel to have free support for all the promised functionality of the > DS-113, but lacks devicetree support to make that functionality > autoconfigurable? that's correct. > That is a beastly spot to be in! yyup. > In that case I'll make > the manual tables from which we can initially code up some tests by using > the gpio driver and later write up the devicetree. yep. > So, sorry for being a bit thick headed, it just dawned on me what our > priorities have to be and why: :) > 1. Hack together some tests under 3.4.104 that we can run on the extant > drivers. > 2. Work on getting extant A20 drivers mainlined in the linux kernel. people have been working on that for many many years. > 3. Create devicetree for DS113 v2.7.4 and v2.7.5, … (all extant versions > of DS113 and microdesktop case). > 4. Work on getting devicetree with add/remove overlay support mainlined in > the linux kernel (and u-boot?). yes. From richard.wilbur at gmail.com Tue Apr 17 23:12:49 2018 From: richard.wilbur at gmail.com (Richard Wilbur) Date: Tue, 17 Apr 2018 16:12:49 -0600 Subject: [Arm-netbook] devicetree and testing In-Reply-To: References: Message-ID: <800B7D4B-E790-4F82-9770-9763264502CC@gmail.com> On Apr 17, 2018, at 15:47, Luke Kenneth Casson Leighton wrote: > > On Tue, Apr 17, 2018 at 9:54 PM, Richard Wilbur > wrote: > […] >> 1. Hack together some tests under 3.4.104 that we can run on the extant >> drivers. >> 2. Work on getting extant A20 drivers mainlined in the linux kernel. > > people have been working on that for many many years. > >> 3. Create devicetree for DS113 v2.7.4 and v2.7.5, … (all extant versions >> of DS113 and microdesktop case). >> 4. Work on getting devicetree with add/remove overlay support mainlined in >> the linux kernel (and u-boot?). > > yes. I understand that people have been working on steps 2 and 4 for years and I had no diminution of their efforts in mind. In my estimation the tasks that can be completed relatively quickly are 1 and 3 as they don't require convincing anyone else of the importance of the goal or merit of the implementation. From lkcl at lkcl.net Tue Apr 17 23:17:25 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Tue, 17 Apr 2018 23:17:25 +0100 Subject: [Arm-netbook] devicetree and testing In-Reply-To: <800B7D4B-E790-4F82-9770-9763264502CC@gmail.com> References: <800B7D4B-E790-4F82-9770-9763264502CC@gmail.com> Message-ID: On Tue, Apr 17, 2018 at 11:12 PM, Richard Wilbur wrote: > I understand that people have been working on steps 2 and 4 for years and I had no diminution of their efforts in mind. absolutely. > In my estimation the tasks that can be completed relatively quickly are 1 and 3 as they don't require convincing anyone else of the importance of the goal or merit of the implementation. it is slightly more complex (3 that is) because a library and associated linux kernel device-driver has to also be written that reads from the I2C EEPROM (to be added to both u-boot and the linux kernel), in order to use the devicetree fragment merging... overlay! that's what it's called. it is *not* going to be okay to just blop in one devicetree file for eoma68-a20-with-microdesktop, one devicetree file for eoma68-rk3288-with-microdesktop, one devicetree file for eoma68-a20-with-laptop-housing, one devicetree file for eoma68-rk3288-with-laptop-housing etc. etc. preventing that kind of insane O(N * M) devicetree proliferation and reducing it down to O(N + M) *IS* the entire point of the EOMA68 initiative. l. From eaterjolly at gmail.com Wed Apr 18 10:27:02 2018 From: eaterjolly at gmail.com (Jean Flamelle) Date: Wed, 18 Apr 2018 05:27:02 -0400 Subject: [Arm-netbook] ikiwiki again Message-ID: Changes are saving, without the page updating| again. "An error occurred while writing CGI reply" From richard.wilbur at gmail.com Wed Apr 18 13:46:55 2018 From: richard.wilbur at gmail.com (Richard Wilbur) Date: Wed, 18 Apr 2018 06:46:55 -0600 Subject: [Arm-netbook] devicetree and testing In-Reply-To: References: <800B7D4B-E790-4F82-9770-9763264502CC@gmail.com> Message-ID: On Apr 17, 2018, at 16:17, Luke Kenneth Casson Leighton wrote: On Tue, Apr 17, 2018 at 11:12 PM, Richard Wilbur wrote: In my estimation the tasks that can be completed relatively quickly are 1 and 3 as they don't require convincing anyone else of the importance of the goal or merit of the implementation. it is slightly more complex (3 that is) because a library and associated linux kernel device-driver has to also be written that reads from the I2C EEPROM (to be added to both u-boot and the linux kernel), in order to use the devicetree fragment merging... overlay! that's what it's called. it is *not* going to be okay to just blop in one devicetree file for eoma68-a20-with-microdesktop, one devicetree file for eoma68-rk3288-with-microdesktop, one devicetree file for eoma68-a20-with-laptop-housing, one devicetree file for eoma68-rk3288-with-laptop-housing etc. etc. preventing that kind of insane O(N * M) devicetree proliferation and reducing it down to O(N + M) *IS* the entire point of the EOMA68 I agree wholeheartedly with the modular mix and match overlay fragment design but saw the software support for it in what I had labelled as priority 4. Whereas I understood priority 3 to entail creating the devicetree fragments for the EOMA hardware that already exists. 1. Hack together some tests under 3.4.104 that we can run on the extant drivers. 2. Work on getting extant A20 drivers mainlined in the linux kernel. 3. Create devicetree [fragments] for DS113 v2.7.4 and v2.7.5, … (all extant versions of DS113 and microdesktop case). 4. Work on getting devicetree with [fragment] add/remove overlay support mainlined in the linux kernel (and u-boot?). Let me restate without relying only on numbers to identify the tasks: We can create the tests to run on 3.4.104 kernel (priority 1) and the devicetree overlays or fragments for each version of the processor card and microdesktop case (priority 3) without buy in from anyone else. Getting the A20 drivers mainlined in the linux kernel (priority 2) and devicetree fragment overlay add/remove support in the linux kernel and u-boot (priority 4) will require continued collaboration with those who maintain the linux kernel and u-boot. Others have already been working on this effort for several years. From lkcl at lkcl.net Wed Apr 18 13:56:09 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Wed, 18 Apr 2018 13:56:09 +0100 Subject: [Arm-netbook] devicetree and testing In-Reply-To: References: <800B7D4B-E790-4F82-9770-9763264502CC@gmail.com> Message-ID: On Wed, Apr 18, 2018 at 1:46 PM, Richard Wilbur wrote: > I agree wholeheartedly with the modular mix and match overlay fragment > design but saw the software support for it in what I had labelled as > priority 4. Whereas I understood priority 3 to entail creating the > devicetree fragments for the EOMA hardware that already exists. ok sorry didn't quite read clearly, just spotted that 3 wasn't clear. looks great to me, richard. From j.neuschaefer at gmx.net Wed Apr 18 14:50:53 2018 From: j.neuschaefer at gmx.net (Jonathan =?utf-8?Q?Neusch=C3=A4fer?=) Date: Wed, 18 Apr 2018 15:50:53 +0200 Subject: [Arm-netbook] devicetree and testing In-Reply-To: References: Message-ID: <20180418135053.tasvav2q6wlbu4xc@latitude> On Tue, Apr 17, 2018 at 02:54:29PM -0600, Richard Wilbur wrote: [...] > So, sorry for being a bit thick headed, it just dawned on me what our > priorities have to be and why: > > 1. Hack together some tests under 3.4.104 that we can run on the extant > drivers. > 2. Work on getting extant A20 drivers mainlined in the linux kernel. In case you haven't seen it (although you probably have), Paul Kocialkowski is working on a mainline driver for the video encode/decode unit in allwinner SoCs: https://bootlin.com/blog/allwinner-vpu-support-in-mainline-linux-status-update-week-15/ > 3. Create devicetree for DS113 v2.7.4 and v2.7.5, … (all extant versions > of DS113 and microdesktop case). > 4. Work on getting devicetree with add/remove overlay support mainlined in > the linux kernel (and u-boot?). BTW, the GPIO nexus patch by Stephen Boyd was merged for 4.17: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd6f2fd5a1d52198468c5cdc3c2472362dff5aaa As far as I understand it, this new syntax will be useful for specifying devicetree overlays that work with multiple different SoCs. Jonathan Neuschäfer From eaterjolly at gmail.com Thu Apr 19 02:53:45 2018 From: eaterjolly at gmail.com (Jean Flamelle) Date: Wed, 18 Apr 2018 21:53:45 -0400 Subject: [Arm-netbook] ikiwiki again In-Reply-To: References: Message-ID: Some volunteers looking at the lastest version [i.e. through the page's source] and test reading what's drafted so far to make sure none of this is too cryptic or vague. Critically thought-out feedback is also highly-appreciated to test comprehension accuracy. --- If anyone disagrees with the fundamental perception of reality, feedback pertaining to that is very much welcome however not a priority unless you have quantifiable evidence of a severe error, such as a demonstrate-ably notable text with an authoritative audience or intuition based on shared or communicable observation. [i.e. videography, scenes in notable fiction with either authoritative authorship or audience, bulletins or bulletinized documentation with either attribute, characteristics of any major language which suggest possible thoughts per the Sapir-Worf hypothesis*, etc] * https://en.wikipedia.org/wiki/The_Languages_of_Pao#Plot_summary * Thoughts aren't made strictly possible by linguistic relativity, however uncommunicable thoughts are likely to get cannibalized and forgotten, by and because of [respectively] communicable ones. Don't get my meaning confused. From lkcl at lkcl.net Thu Apr 19 03:15:48 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Thu, 19 Apr 2018 03:15:48 +0100 Subject: [Arm-netbook] ikiwiki again In-Reply-To: References: Message-ID: On Thu, Apr 19, 2018 at 2:53 AM, Jean Flamelle wrote: > If anyone disagrees with the fundamental perception of reality, > * https://en.wikipedia.org/wiki/The_Languages_of_Pao#Plot_summary > * Thoughts aren't made strictly possible by linguistic relativity, https://en.wikipedia.org/wiki/Linguistic_relativity i illustrate this example with one from Neal Stephenson's "Cryptonomicon" in which one of the characters is described as a "drug addict" (noun). no longer a human being (noun), a (noun) drug addict. in german an adverb would be used. "Ah, you are morphine hyphen seeky?" would be the literal translation. as in, "you are a human being, with a BEHAVIOURAL QUALIFIER that tends to convey on you a propensity to seek out morphine?" absolutely huge, huge difference. another example is sanskrit, "Thank God I am alive HYPHEN childed" taking a NOUN (child), turning it into an ADVERB (child-ed), and using it as a german-style qualifier of a VERB. which is incredibly powerful. it says: "thank god i am alive" "thank god my children are alive" "thank god i am alive at the same simultaneous time as my children happen to be alive (focus on the relief of the simultaneity)" "thank GOD (focus on celebration) at the same simultaneous time as my children happen to be alive" there were several more subtle implications when i examined this 20 years ago, most of which i've forgotten. From lkcl at lkcl.net Thu Apr 19 05:19:16 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Thu, 19 Apr 2018 05:19:16 +0100 Subject: [Arm-netbook] devicetree and testing In-Reply-To: <20180418135053.tasvav2q6wlbu4xc@latitude> References: <20180418135053.tasvav2q6wlbu4xc@latitude> Message-ID: --- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, Apr 18, 2018 at 2:50 PM, Jonathan Neuschäfer wrote: > On Tue, Apr 17, 2018 at 02:54:29PM -0600, Richard Wilbur wrote: > [...] >> So, sorry for being a bit thick headed, it just dawned on me what our >> priorities have to be and why: >> >> 1. Hack together some tests under 3.4.104 that we can run on the extant >> drivers. >> 2. Work on getting extant A20 drivers mainlined in the linux kernel. > > In case you haven't seen it (although you probably have), Paul > Kocialkowski is working on a mainline driver for the video encode/decode > unit in allwinner SoCs: > > https://bootlin.com/blog/allwinner-vpu-support-in-mainline-linux-status-update-week-15/ great! we like paul. >> 3. Create devicetree for DS113 v2.7.4 and v2.7.5, … (all extant versions >> of DS113 and microdesktop case). >> 4. Work on getting devicetree with add/remove overlay support mainlined in >> the linux kernel (and u-boot?). > > BTW, the GPIO nexus patch by Stephen Boyd was merged for 4.17: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd6f2fd5a1d52198468c5cdc3c2472362dff5aaa > > As far as I understand it, this new syntax will be useful for specifying > devicetree overlays that work with multiple different SoCs. thx jonathan. From bob at fourtheye.org Thu Apr 19 12:31:34 2018 From: bob at fourtheye.org (Robert Wilkinson) Date: Thu, 19 Apr 2018 13:31:34 +0200 Subject: [Arm-netbook] ikiwiki again In-Reply-To: References: Message-ID: <20180419113134.GB26299@fourtheye.org> On Thu, Apr 19, 2018 at 03:15:48AM +0100, Luke Kenneth Casson Leighton wrote: > On Thu, Apr 19, 2018 at 2:53 AM, Jean Flamelle wrote: > > > If anyone disagrees with the fundamental perception of reality, > > > * https://en.wikipedia.org/wiki/The_Languages_of_Pao#Plot_summary > > * Thoughts aren't made strictly possible by linguistic relativity, > > https://en.wikipedia.org/wiki/Linguistic_relativity I guess I should post the obligatory youtube link, especially since it features a certain Mr. Albert Einstein erm singing? https://www.youtube.com/watch?v=lLl8vvKc7Ak Bob -- Agree with them now, it will save so much time. From chadvellacott at sasktel.net Tue Apr 24 23:13:08 2018 From: chadvellacott at sasktel.net (Chadvellacott) Date: Tue, 24 Apr 2018 16:13:08 -0600 Subject: [Arm-netbook] will lap-top really be 1.1 kg, and how wide Message-ID: <3e7c5ec5-46a5-e674-1e6c-2176b30ee074@sasktel.net> I noticed that the campaign's main page on "Crowd Supply", says "Only 1.1 kg weight" for the lap-top. Is this specification, still part of the plan? And how wide is the lap-top planned to be (from the left edge of the case, to the right edge, across the key-board)? (I imagine that 15.6 inches is for the screen itself rather than the whole case, and is a diagonal measurement.) From calmstorm at posteo.de Wed Apr 25 01:22:59 2018 From: calmstorm at posteo.de (zap) Date: Tue, 24 Apr 2018 20:22:59 -0400 Subject: [Arm-netbook] will lap-top really be 1.1 kg, and how wide In-Reply-To: <3e7c5ec5-46a5-e674-1e6c-2176b30ee074@sasktel.net> References: <3e7c5ec5-46a5-e674-1e6c-2176b30ee074@sasktel.net> Message-ID: <203a883c-e16b-6335-9ac6-daf8387e03cd@posteo.de> First, I don't represent Luke, but given what he has said in the past, On 04/24/18 18:13, Chadvellacott wrote: >    I noticed that the campaign's main page on "Crowd Supply", says > "Only 1.1 kg weight" for the lap-top.  Is this specification, still > part of the plan? > I don't see why not, the storage drive isn't an ssd nor is it a hdd.  Also the battery is not a 9 cell, a 6 cell or even a 3 cell. 1 cell. Also, I imagine it has very few wires/components inside of it. No wifi card or ethernet card instead it uses wifi adapter usb. I guess my point is, I don't see why it wouldn't be really close to that description. >    And how wide is the lap-top planned to be (from the left edge of > the case, to the right edge, across the key-board)?  (I imagine that > 15.6 inches is for the screen itself rather than the whole case, and > is a diagonal measurement.) As for this, I cannot comment at all. Luke did tell me once that it would seem more like a 14 inch. At least that's what I recall anyways him telling me. *(**I asked WAY TOO MANY QUESTIONS*!*) *But yeah, unless someone else reponds and says otherwise, who knows about the project I assume that's the answer you'll get. ** > > _______________________________________________ > arm-netbook mailing list arm-netbook at lists.phcomp.co.uk > http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook > Send large attachments to arm-netbook at files.phcomp.co.uk From lkcl at lkcl.net Wed Apr 25 04:39:12 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Wed, 25 Apr 2018 04:39:12 +0100 Subject: [Arm-netbook] will lap-top really be 1.1 kg, and how wide In-Reply-To: <3e7c5ec5-46a5-e674-1e6c-2176b30ee074@sasktel.net> References: <3e7c5ec5-46a5-e674-1e6c-2176b30ee074@sasktel.net> Message-ID: On Tue, Apr 24, 2018 at 11:13 PM, Chadvellacott wrote: > I noticed that the campaign's main page on "Crowd Supply", says "Only 1.1 > kg weight" for the lap-top. yes. no metal except that of the LCD (which i recall was 400g). no SSD, no HDD, no fans, no heatsinks (except the metal of the keyboard is in direct contact with the metal of the CPU Card case). it's a good illustration of the "mass decompounding" effect, a phrase first used in the vehicle industry. > And how wide is the lap-top planned to be (from the left edge of the > case, to the right edge, across the key-board)? you can check for yourself by downloading the GPLv3-licensed 3D CAD source code. https://www.youmagine.com/designs/libre-hardware-licensed-parametric-laptop-design/ > (I imagine that 15.6 inches > is for the screen itself rather than the whole case, and is a diagonal > measurement.) the LCD is listed on the rhombus-tech page, from which the datasheet may be sourced, and there is approximately 2mm left and right, about 10mm top, about.... 25mm at the bottom. that gives the overall dimensions. l. From chadvellacott at sasktel.net Wed Apr 25 16:30:16 2018 From: chadvellacott at sasktel.net (Chadvellacott) Date: Wed, 25 Apr 2018 09:30:16 -0600 Subject: [Arm-netbook] will lap-top really be 1.1 kg, and how wide In-Reply-To: References: <3e7c5ec5-46a5-e674-1e6c-2176b30ee074@sasktel.net> Message-ID: <1b00c5ac-1b22-ee59-de16-958ce96c940b@sasktel.net> Luke Kenneth Casson Leighton wrote on 2018/04/24 9:39 PM: > On Tue, Apr 24, 2018 at 11:13 PM, Chadvellacott > wrote: ~ >> And how wide is the lap-top planned to be (from the left edge of the >> case, to the right edge, across the key-board)? > > you can check for yourself by downloading the GPLv3-licensed 3D CAD > source code. > https://www.youmagine.com/designs/libre-hardware-licensed-parametric-laptop-design/ > That page said "The parts are deliberately designed to be printable on a standard 200x200mm Mendel90 style 3D printer, so that even a 15.6in laptop may be created by printing the longest parts (260mm) across the diagonal of a Mendel90 print bed (280mm)." But I guess that 260 mm is not meant to span the whole back of the screen, considering things lower down on this message. > >> (I imagine that 15.6 inches >> is for the screen itself rather than the whole case, and is a diagonal >> measurement.) > > the LCD is listed on the rhombus-tech page, from which the datasheet > may be sourced, and there is approximately 2mm left and right, about > 10mm top, about.... 25mm at the bottom. > > that gives the overall dimensions. Yes, the "youmagine"-page led to http://rhombus-tech.net/community_ideas/laptop_15in/news/ to http://rhombus-tech.net/community_ideas/laptop_15in/ to "AUO B156XTN02.2" for LCD, from which "duckduckgo" led to http://www.panelook.com/B156XTN02.2_AUO_15.6_LCM_parameter_15249.html which said "outline size of 359.3(W)×209.5(H)×5.5(D) mm" I did not get the "PDF"-data-sheet offered there, because I do not have login-credentials there. But the quoted numbers are probably correct, and are confirmed by http://www.lcd-source.com/Product_Specifications_AUO_B156XTN02.2 359.3 mm width of LCD, plus 2 mm on the left, plus 2 mm on the right, is 363.3 mm, or about 14.3 inches wide for the top part of the "clam-shell". Thanks for the directing. That about answers my question. > > l. From lkcl at lkcl.net Thu Apr 26 00:08:28 2018 From: lkcl at lkcl.net (Luke Kenneth Casson Leighton) Date: Thu, 26 Apr 2018 00:08:28 +0100 Subject: [Arm-netbook] will lap-top really be 1.1 kg, and how wide In-Reply-To: <1b00c5ac-1b22-ee59-de16-958ce96c940b@sasktel.net> References: <3e7c5ec5-46a5-e674-1e6c-2176b30ee074@sasktel.net> <1b00c5ac-1b22-ee59-de16-958ce96c940b@sasktel.net> Message-ID: --- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, Apr 25, 2018 at 4:30 PM, Chadvellacott wrote: > Luke Kenneth Casson Leighton wrote on 2018/04/24 9:39 PM: >> >> On Tue, Apr 24, 2018 at 11:13 PM, Chadvellacott >> wrote: > > ~ >>> >>> And how wide is the lap-top planned to be (from the left edge of the >>> case, to the right edge, across the key-board)? >> >> >> you can check for yourself by downloading the GPLv3-licensed 3D CAD >> source code. >> >> https://www.youmagine.com/designs/libre-hardware-licensed-parametric-laptop-design/ >> > That page said "The parts are deliberately designed to be printable on a > standard 200x200mm Mendel90 style 3D printer, so that even a 15.6in laptop > may be created by printing the longest parts (260mm) across the diagonal of > a Mendel90 print bed (280mm)." > But I guess that 260 mm is not meant to span the whole back of the > screen, considering things lower down on this message. that's the vertical. case is thus divided into 7 separate parts for LCD and 7 main structural parts for the body. vertical @ 260mm left right middle horizontal @ 160mm (appx): front left front right back left back right it's... complicated. >> >> >>> (I imagine that 15.6 inches >>> is for the screen itself rather than the whole case, and is a diagonal >>> measurement.) >> >> >> the LCD is listed on the rhombus-tech page, from which the datasheet >> may be sourced, and there is approximately 2mm left and right, about >> 10mm top, about.... 25mm at the bottom. >> >> that gives the overall dimensions. > > > Yes, the "youmagine"-page led to > http://rhombus-tech.net/community_ideas/laptop_15in/news/ > to > http://rhombus-tech.net/community_ideas/laptop_15in/ > to > "AUO B156XTN02.2" for LCD, > from which "duckduckgo" led to > http://www.panelook.com/B156XTN02.2_AUO_15.6_LCM_parameter_15249.html > which said > "outline size of 359.3(W)×209.5(H)×5.5(D) mm" there you go. > I did not get the "PDF"-data-sheet offered there, because I do not have > login-credentials there. But the quoted numbers are probably correct, and > are confirmed by > http://www.lcd-source.com/Product_Specifications_AUO_B156XTN02.2 > > 359.3 mm width of LCD, plus 2 mm on the left, plus 2 mm on the right, is > 363.3 mm, or about > > 14.3 inches wide for the top part of the "clam-shell". > > Thanks for the directing. That about answers my question. >> >> >> l. > > > _______________________________________________ > arm-netbook mailing list arm-netbook at lists.phcomp.co.uk > http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook > Send large attachments to arm-netbook at files.phcomp.co.uk