arm-netbook

arm-netbook@lists.phcomp.co.uk

1079 discussions

Re: [Arm-netbook] usb keyboard, width about 15cm?
by ronwirring＠Safe-mail.net 31 May '17

31 May '17

-------- Original Message -------- From: Christopher Havel <laserhawk64(a)gmail.com> Apparently from: arm-netbook-bounces(a)lists.phcomp.co.uk To: Eco-Conscious Computing <arm-netbook(a)lists.phcomp.co.uk> Subject: Re: [Arm-netbook] usb keyboard, width about 15cm? Date: Sat, 27 May 2017 13:10:26 -0400 > The Bluetooth keyboards are Bluetooth only. > > Wired USB keyboard, that size? Never seen one. Would love to have one http://usb.brando.com/prod_detail.php?prod_id=00666 > myself; I've wanted to homebrew a waist-pack PC with wrist keyboard and > "google glass" style screen, since approximately a half hour after the dawn > of time. I've even got a viewfinder CRT out of an old camcorder that I > could use as the display if I hooked it up right. Trouble is I don't trust > BT to not interfere with everyone else and screw me up too... that, and I'd > need to make it work with a battery. > > Now that I think about it... I think I've seen one such keyboard literally > once ever, either by luck on eBay or on some other website. Don't remember > since it was at least five years ago. The thing commanded a princely sum, > too... like $150. > > It occurs to me as well that you might be able to get an > industrial/commercial duty wrist PC off eBay (be prepared to pay multiple > hundreds of dollars) and doof around with its built-in keyboard... or do > something with part of a cell phone and a Teensy... but that's real > jerry-rigging at best. There are also keyboards floating around for old > IPAQ PDAs that may be useful somehow... but you'd have to reverse-engineer > them and they look like they'd be horrible to use to begin with, you don't > even get most PC function keys (TAB, CTRL, ALT, etc). > > Good luck, and let me know if you find one... > _______________________________________________ > arm-netbook mailing list arm-netbook(a)lists.phcomp.co.uk > http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook > Send large attachments to arm-netbook(a)files.phcomp.co.uk

5 5

Re: [Arm-netbook] Side-Topic: Liberating PocketCHIP
by David Niklas 30 May '17

30 May '17

On Mon, 08 May 2017 09:59:50 +0100 "mike.valk(a)gmail.com" <mike.valk(a)gmail.com> wrote: > 2017-05-08 3:34 GMT+02:00 <doark(a)mail.com>: > > > I apologize for DOS'ing the list, I can only get online about once a > > week. > > > > On Thu, 4 May 2017 17:13:23 +0200 > > "mike.valk(a)gmail.com" <mike.valk(a)gmail.com> wrote: > > > > > > 2017-05-04 9:04 GMT+02:00 John Luke Gibson <eaterjolly(a)gmail.com>: > > > > > > > Since it seems like a trivially simple task that for some reason > > > > no one has taken up, I would like to take the opportunity to > > > > exercise a learning experience and simultaneously benefit the > > > > community, by liberating PocketCHIP by deblobbing the source and > > > > re-compiling. > > > > > > The PocketCHIP is powered by their SoM: > > > http://linux-sunxi.org/NextThingCo_CHIP > > > > > > That is apparently a Allwinner R8 pared with an external rtl8723bs > > > Wifi/BT chip. > > > > > > The R8 is a rebranded A13. > > What? I own one of those and I'm almost certain that the CPU is an A7. > > Let's boot the PocketCHIP up... > > The processor is detected as an A7. > > > > It should be a Cortex-A8. > http://linux-sunxi.org/Allwinner_SoC_Family > > The new chip GR8, which is specific SoC for NextThingCo, seems to be an > "sun5i" as well. Also a slightly modified A13 I guess. > > The're seems to but mainline support for it. Icenowy Zheng has addid it > I think. But the'res no wiki page fo it. > http://linux-sunxi.org/Linux_mainlining_effort > http://linux-sunxi.org/GR8 Sorry, I (foolishly) though that ARMv7 == A7 (i.e. a contraction). > > > I'll attach the output, it would probably be interesting to see all of > > it... > > Done, it's compressed bzip2 since it's ~300KiB decompressed which is > > large for an email. > > > > Use pastebin or sorts. Or just cut out the specifica part. > Sorry, I thought the rest of it might be useful to look at. <snip> > > You're not giving us enough details. Who is Verhaegen? What did he > > burn out on? > > When I first considered purchasing a PocketCHiP I read about the GPU > > not having 3D capabilities because of a binary blob. So, the CHIP > > folks hired (I think it was an extended goal of the kickstarter > > campaign), a kernel dev to add support to the Linux kernel for the > > GPU. > > > That did not happen. The're is no Opensource linux driver for MALI. NTC > hardly involves itself with the linux-sunxi community. > > Their website is hardly obvious to the software needs of running their > hardware. > > How hard can it be.... > > "To use our hardware you have two options: Our BSP which has closed > source drivers, but you have full utilization of the hardware. Or use > the mainline kernel with some restrictions" Where is that quote from? > And state your involvement in freeing the hardware or not. > > NTC website is just one big selling machine. > Prior to purchasing the Pocket CHIP I read their docs and kickstarter page. See this (their kickstarter page says similar): https://docs.getchip.com/chip.html#is-chip-open-source-where-are-the-docs Are they flat out lying? Thanks, David

4 3

Re: [Arm-netbook] firefly 3399 all source software disclosed?
by David Niklas 30 May '17

30 May '17

On Mon, 8 May 2017 05:45:36 +0100 Luke Kenneth Casson Leighton <lkcl(a)lkcl.net> wrote: > --- > crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 > > > On Sun, May 7, 2017 at 10:10 PM, zap <zapper(a)openmailbox.org> wrote: > > > > > > On 05/07/2017 04:29 PM, ronwirring(a)Safe-mail.net wrote: > >> All software for the mali-t860 is open source? > > none. MALI is proprietary. I'm confused. Luke, if you plan on making an RK3399 into an eoma project how can you get RYF status if the mali GPU is closed source? For that matter, how can you get RYF cert. for your current eoma68 project? Unless I'm mistaken and it uses a different GPU? Or you just leave the HW crippled? Thanks, David

3 2

Re: [Arm-netbook] rk3399 what full schematics does lkcl want?
by David Niklas 30 May '17

30 May '17

On Fri, 19 May 2017 18:17:16 +0100 Luke Kenneth Casson Leighton <lkcl(a)lkcl.net> wrote: > --- > crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 > > > On Fri, May 19, 2017 at 4:49 PM, <ronwirring(a)safe-mail.net> wrote: <snip> > > Because a license prohibits it? > > no. > > > Because competitors can use them? > > correct. > > > Lkcl, have you asked tfirefly to give you the full schematics cad > > data? > > no... because they would think i was a bit dumb. or worse, wanted to > steal their business. i have no desire to piss them off. > > > > Because I got to think, you said tfirefly is withholding some > > schematics, > > no i did not say that. it may be true but i would not have > specifically said it. i may have said that *rockchip* has *not made > available the reference design* which is a totally different matter. > > you may have then thought "rockchip equals firefly". > > please try not to make cross-connections and/or correlations that > aren't actually the case. > > > > I wrote tfirefly asking them to email me the full schematics. > > Tfirefly never denied, that they had not made the full schematics > > public. They said, they could not disclose the full schematics. Maybe > > due to a lack of english skills on both sides. > > no, you've just misunderstood their business model. please don't ask > them again, it's not fair to ask them to make public something which > will destroy their business model. > > > > Then what should you ask tfirefly for? Full schematics cad data? > > absolutely nothing. you don't ask them for anything. they're a > third party business - an OEM. > > and we also can't ask rockchip either, because we're not going to > order a million of their processors, cash up-front... *until* they > have made full CAD data available. > > classic catch 22 situation. > > so instead we wait - as i specifically, specifically said - until > rockchip's Reference Designs leak out onto the public internet and are > available on e.g. taobao or other site, for sale for $25. > > l. So, how did the t-firefly group create their SOC if they could not get the CAD files? Thanks, David

2 2

molex 12v 5v 2a power supply together with 3 way usb otg host charger cable
by ronwirring＠Safe-mail.net 30 May '17

30 May '17

https://www.amazon.com/Coolerguys-100-240v-Molex-Power-Adapter/dp/B000MGG6S… Can you power supply the pc card with the 5v 2a part of the power supply in combination with the 3 way usb otg host charger cable? Thank you.

3 4

Re: [Arm-netbook] first prototype microdesktop casework
by David Niklas 30 May '17

30 May '17

On Mon, 8 May 2017 18:51:21 +0100 Luke Kenneth Casson Leighton <lkcl(a)lkcl.net> wrote: > > On Mon, May 8, 2017 at 2:07 AM, <doark(a)mail.com> wrote: > > > I own a Reach3D printer. It's an all aluminum housing and z axis gear > > printer. I'm still in the construction phase, but if me and my caliper > > (it's auto-calibrating but I want it perfect :) work well together > > then I should be printing sometime around the 21st. I could help you > > with my printer at limited expense (unless something big happens in > > my life :) > > one piece of advice: buy some printbite, stick it to the aluminium > plate (after cleaning it - do follow PRECISELY the instructions for > printbite installation). better, get a MK3 (aluminium) bed plate, > because having a MK2 not in full contact with the aluminium is a pain > (uneven heat distribution and transfer). i've currently stacked some > cardboard underneath to make the MK2 stop bowing downwards... > *sigh*... > > printbite will stop a world of pain in both making prints stick and > also getting them off. but *read and follow the instructions*. > > l. Actually, I was thinking of using a lokibuild sheet (another kickstatr? thing (seems I have lost the link...)): here is one of the right size? https://shop3duniverse.com/collections/accessories/products/3d-universe-lok… Thanks, David

2 2

Re: [Arm-netbook] Micro desktop corner design
by Luke Kenneth Casson Leighton 30 May '17

30 May '17

On Tue, May 30, 2017 at 5:09 AM, Tor, the Marqueteur <Marqueteur(a)fineartmarquetry.com> wrote: > On 29/05/17 16:56, Luke Kenneth Casson Leighton wrote: > ...snip... >>> 1. Am I right that the front right corner actually only needs a single >>> wide dado on the inside face for the eject button? >> >> yes. >> >>> 2. Do any of the components on the other three corners need cutouts, >> >> no. >> >>> or are they back just far enough to clear? >> >> yes. > > Then, presuming I can find a router bit within tolerance for the height > of the eject button, it looks like I could do this design as is for the > corners. if i thin down the parts on the inner edge i could potentially do away with the need for the eject button inset entirely. i also want to bring out the PCB cut through to the front so that you can do a straight-through cut with a router @ around 1.8 to 2.0mm. l.

1 0

postMarketOS : good fit for EOMA50/68?
by Mike Leimon 30 May '17

30 May '17

Announcement of this project has been making the rounds lately and I think that it might be an excellent fit for an EOMA50 based phone/tablet (if and when those designs materialize). https://ollieparanoid.github.io/post/postmarketOS/ Currently they are targeting only old phone hardware however, I think that their concept would work well for any phone/touchscreen device that is designed to have a long useful life. I may be wrong but, I think a OS distribution of this nature would be an excellent complement to computing hardware that is also designed to last much longer than the current norm. -Mike

1 0

Re: [Arm-netbook] libre 64-bit risc-v SoC
by David Niklas 30 May '17

30 May '17

On Mon, 8 May 2017 06:24:08 +0100 Luke Kenneth Casson Leighton <lkcl(a)lkcl.net> wrote: > On Mon, May 8, 2017 at 4:00 AM, David Niklas <doark(a)mail.com> wrote: <snip> > >> > important to avoid, because mixed analog and digital is incredibly > >> > hard to get right. also note that things like HDMI, SATA, and even > >> > ethernet are quite deliberately NOT on the list. Ethernet RMII > >> > (which is digital) could be implemented in software using a minion > >> > core. the advantage of using the opencores VGA (actually LCD) > >> > controller is: i already have the full source for a *complete* > >> > linux driver. > > > > Considering that analog was around *long* before digital I'm surprised > > that it is "Hard to get right", > > analog isn't "hard". digital isn't "hard". specifically *MIXING* > them is ultra-hard. > > > is there a reason for this? > > completely different processes and design criteria. the restrictions > (design rules) placed on digital ASIC layouts have to be adhered to in > the *analog* areas: you can't just change the stack to suit the analog > areas. i don't know the full details, but i know someone with 30 > years experience of working with ASICs who does. > > > Isn't there a chip for just this kind of thing? > > no. not a custom one... and we're taking custom ASICs. Forgive me for contradicting you again, but don't all computers that have a MIC in jack using some sort of analog to digital converter? And vice-versa with Headphone out? I think they all use PCM. Would such a converter be suitable? Why? Thanks, David

2 1

Re: [Arm-netbook] Micro desktop corner design
by Luke Kenneth Casson Leighton 30 May '17

30 May '17

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Mon, May 29, 2017 at 7:38 PM, Tor, the Marqueteur <Marqueteur(a)fineartmarquetry.com> wrote: > Aloha Luke, > > I sent this to the list a couple times, but it hasn't shown up and nor > have any replies, so I'm sending it to you. I don't think anything's > changed with my email that should have done it, but maybe you'll see > something on the backend now that you know to look. > > Thanks, > Tor > > > Aloha, > > I just came across the page still up on my browser, and ended up with a > couple questions about the design as it stands now. > > 1. Am I right that the front right corner actually only needs a single > wide dado on the inside face for the eject button? yes. > 2. Do any of the components on the other three corners need cutouts, no. > or are they back just far enough to clear? yes.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

arm-netbook