mikey_w has quit [Remote host closed the connection]
voronaam has quit [Quit: Leaving.]
jquip has joined #arm-netbook
tinti has quit [Ping timeout: 255 seconds]
mikey_w has joined #arm-netbook
stefanro1 has quit [Ping timeout: 255 seconds]
bsdfox has joined #arm-netbook
bsdfox has joined #arm-netbook
bsdfox has quit [Changing host]
stefanro has joined #arm-netbook
jquip has quit [Quit: jquip]
<ManoftheSea>
hmm, dang. So, I've got the script.bin from the device. I've got u-boot built from hno's source, putting spl at 8k and uboot.bin at 32k. I have a vFat partition, and a boot.scr that (supposedly) loads it all.
<ManoftheSea>
uboot was configured for mk802ii, and all compiled with arm-linux-gnueabihf-gcc-4.7
<ManoftheSea>
still, no boot.
* ManoftheSea
sadface
<ManoftheSea>
hno: the u-boot wiki on your github says to send you script.bin for devices. Do you want from the mk802ii, or do you already have?
ZaEarl_ has joined #arm-netbook
ZaEarl has quit [Read error: Connection reset by peer]
tinti has joined #arm-netbook
ZaEarl_ has quit [Ping timeout: 244 seconds]
popolon has quit [Quit: Quitte]
tinti has quit [Ping timeout: 250 seconds]
rsalveti has quit [Ping timeout: 240 seconds]
jquip has joined #arm-netbook
<jquip>
u-boot.bin of mele is the safest bet to try for unknown hardware right?
<jquip>
a1000
<jquip>
from the hwpack
<jquip>
have a generic 512 mb tablet which I wanted to probe for specs
<jquip>
hno ?
<jquip>
ManoftheSea: you can try u-boot.bin from the hwpacks ... a1000, sometimes, pressing the power on button for about 5-10 secs helps
<jquip>
also do you have serial to ttl ?
<jquip>
that's the only way to check u-boot related problems
<ManoftheSea>
"power on button"?
<ManoftheSea>
no, I don't yet have the usb-ttl-uart
<ManoftheSea>
The mk802 doesn't have a power button. It doesn't have any buttons.
aholler_ has joined #arm-netbook
<jquip>
ahh sorry... i thought you had a tablet for some begone reason...
<ManoftheSea>
Thanks for the help.
<Mehhh>
Man, it has a reset button
aholler has quit [Ping timeout: 244 seconds]
<jquip>
well that need not be depressed for so long ... usually some odd tablets require the power on button to be pressed like that... not the reset button..
<ManoftheSea>
oh? this one labeled "recover"?
<ManoftheSea>
I didn't recognize it as a button.
<jquip>
erm.. I dont have a mk802 :( so i wouldn't be able to say..
<ManoftheSea>
crap... where are the ports on this?
<ManoftheSea>
So... I've got 8 pads in what looks like a uSD size.
<ManoftheSea>
tront, trsclk, rsoat, spen?
jquip has left #arm-netbook [#arm-netbook]
Quarx has joined #arm-netbook
gimli has joined #arm-netbook
antonl has joined #arm-netbook
gsilvis has quit [Read error: Connection reset by peer]
gsilvis has joined #arm-netbook
atari2600a has quit [Remote host closed the connection]
<ManoftheSea>
root partition should contain: boot.scr, script.bin (from fex?), and uImage, right? And that's it?
oliv3r has quit [Read error: Operation timed out]
ol1ver has quit [Ping timeout: 240 seconds]
gimli has quit [Remote host closed the connection]
eFfeM has quit [Read error: Connection reset by peer]
eFfeM1 has joined #arm-netbook
specing has quit [Quit: Oops, wrong button]
specing has joined #arm-netbook
Quarx has joined #arm-netbook
eFfeM1 has quit [Quit: Leaving.]
eFfeM has joined #arm-netbook
eFfeM has quit [Client Quit]
eFfeM has joined #arm-netbook
DEAT_ has quit [Read error: Connection reset by peer]
DEAT_ has joined #arm-netbook
eFfeM1 has joined #arm-netbook
eFfeM has quit [Ping timeout: 260 seconds]
eFfeM has joined #arm-netbook
eFfeM1 has quit [Client Quit]
ol1ver has joined #arm-netbook
oliv3r has joined #arm-netbook
aholler_ has quit [Quit: 3.7]
eFfeM has quit [Quit: Leaving.]
eFfeM has joined #arm-netbook
aholler has joined #arm-netbook
Guest38025 is now known as fredy
eFfeM has quit [Quit: Leaving.]
eFfeM has joined #arm-netbook
arokux1 has quit [Ping timeout: 248 seconds]
arokux1 has joined #arm-netbook
tinti has joined #arm-netbook
tinti has quit [Ping timeout: 264 seconds]
eFfeM has quit [Quit: Leaving.]
eFfeM has joined #arm-netbook
eFfeM has quit [Read error: Connection reset by peer]
eFfeM has joined #arm-netbook
lerc_ has joined #arm-netbook
lerc has quit [Ping timeout: 264 seconds]
popolon has joined #arm-netbook
Mehhh has quit [Quit: Page closed]
eFfeM has quit [Quit: Leaving.]
eFfeM has joined #arm-netbook
eFfeM has quit [Read error: Connection reset by peer]
eFfeM1 has joined #arm-netbook
eFfeM1 has quit [Read error: Connection reset by peer]
eFfeM has joined #arm-netbook
eFfeM has quit [Client Quit]
eFfeM1 has joined #arm-netbook
eFfeM1 has quit [Read error: Connection reset by peer]
eFfeM has joined #arm-netbook
eFfeM has quit [Client Quit]
eFfeM has joined #arm-netbook
tinti has joined #arm-netbook
eFfeM has quit [Read error: Connection reset by peer]
eFfeM has joined #arm-netbook
eFfeM has quit [Quit: Leaving.]
eFfeM has joined #arm-netbook
eFfeM1 has joined #arm-netbook
eFfeM has quit [Client Quit]
eFfeM1 has quit [Ping timeout: 256 seconds]
eFfeM has joined #arm-netbook
eFfeM has quit [Client Quit]
eFfeM has joined #arm-netbook
eFfeM has quit [Client Quit]
eFfeM has joined #arm-netbook
eFfeM has quit [Ping timeout: 255 seconds]
eFfeM has joined #arm-netbook
eFfeM has quit [Read error: Connection reset by peer]
eFfeM has joined #arm-netbook
eFfeM has quit [Read error: Connection reset by peer]
eFfeM has joined #arm-netbook
eFfeM1 has joined #arm-netbook
eFfeM has quit [Read error: Connection reset by peer]
Ershov has quit [Ping timeout: 264 seconds]
eFfeM1 is now known as eFfeM
Ershov has joined #arm-netbook
DEAT_ has quit [Read error: Connection reset by peer]
DEAT_ has joined #arm-netbook
ssspiff has quit [Ping timeout: 264 seconds]
sspiff has joined #arm-netbook
rz2k has joined #arm-netbook
lerc_ has quit [Ping timeout: 264 seconds]
lerc has joined #arm-netbook
<mnemoc>
allwinner removed the A20 product page....
<libv>
aw :(
<orly_owl>
<violins>
jquip has joined #arm-netbook
<rellla>
for re-design ;-)
<orly_owl>
woooooooo
soooge has joined #arm-netbook
<mripard>
mnemoc: of course, if you add the cortex-a* to the mess... :)
Sv has quit [Read error: Connection reset by peer]
antonl has quit [Ping timeout: 250 seconds]
Sv has joined #arm-netbook
<oliv3r>
do we know for certain it's a powerVR gpu now? with the same cedarx
<orly_owl>
boo
<slapin>
hi, all!
<slapin>
does a7 core is much worse that a8 core?
sspiff has quit [Ping timeout: 252 seconds]
<RaYmAn>
slapin: no, it's better, at least watt vs raw cpu power
sspiff has joined #arm-netbook
<mnemoc>
mripard: :)
<mnemoc>
rellla: I think they are hidding it to not compete with the A31 yet
<mnemoc>
rellla: A20 references were removed from most of the pages where it was linked from
rsalveti has joined #arm-netbook
<rellla>
mnemoc: allwinner should invest more time in supporting cedary than hiding a20 :o
<rellla>
s/cedary/cedarx/
<ibot>
rellla meant: mnemoc: allwinner should invest more time in supporting cedarx than hiding a20 :o
<oliv3r>
allwinner should release proper documentation to all their chips for proper gpl support :D
<oliv3r>
nand+cedarx to start with
<jinzo>
and then we all wake up
<phh>
slapin: A7 is mostly as fast as A9
<mnemoc>
for less power
merbanan has quit [Read error: Operation timed out]
<oliv3r>
oh, is it time to go home allready?
<oliv3r>
:p
<oliv3r>
mnemoc: i really wanna continue working on the wiki; but i'm horribly stuck (i think, i haven't thought abou tit anymore) about those stupid templates :)
<oliv3r>
i've made something though
<oliv3r>
i'll maybe think a little abou tit again tomorrow and continue
ol1ver has quit [Ping timeout: 256 seconds]
oliv3r has quit [Read error: Operation timed out]
ol1ver has joined #arm-netbook
<mnemoc>
ol1ver: :)
* rellla
wishes to find some guys from allwinner in this channel to be able to talk directly ;)
<mnemoc>
the only person from allwinner who ever came here was tom, and he doesn't work for allwinner anymore
Mehhh has joined #arm-netbook
soooge has quit [Ping timeout: 248 seconds]
oliv3r has joined #arm-netbook
<rellla>
and the second person to complete allwinner is
nemik_ is now known as nemik
<rellla>
eva iirc? ;-)
soooge has joined #arm-netbook
merbanan has joined #arm-netbook
jquip has quit [Ping timeout: 248 seconds]
<mnemoc>
techn_: anything to comment regarding Hans de Goede's patch for hdmi_core ?
avernos has quit [Ping timeout: 246 seconds]
<traeak>
a7 is later design than a9 i think
<mnemoc>
mripard: to add more mess to the naming thing, olimex is preparing an A10s based olinuxino, which is also sun5i ;-)
<mnemoc>
traeak: the A7 is ISA equivalent to the A15. so yes, much newer than A9
<mripard>
mnemoc: aaargh :)
<mnemoc>
mripard: :)
<traeak>
i want stuff based on lkcl's new 8 core dealey which should be open
<traeak>
somneone comes up with an SOC that doesn't need tons of proprietary crap they automagically get a whole market
<traeak>
if the SOC isn't hugely expensive that is
<mnemoc>
traeak: the icubetech thing?
<traeak>
mnemoc: yeah, that dealy
<mnemoc>
mripard: in the case of the boards we are probably better sticking with product names "a13-olinuxino" in this case
<mnemoc>
vinifm: if you are going to write a kernel driver, begin respecting the linux coding style
<vinifm>
I assumed that kmalloc allocates memory for all members
<jquip>
Hallo hno: yep ... roger that ... a10_mid_512mb coming up soon .. I haven't been able to get good pics of the boards yet... will see tomorrow
<mnemoc>
vinifm: kzalloc *tries* to allocate the requested number of bytes, it doesn't care about your struct at all
<mnemoc>
vinifm: that's your job
<vinifm>
so 'struct i2c_client *client;' is NULL? Line 37
<mnemoc>
vinifm: after allocating an struct eep_bank, yes. it's NULL
<vinifm>
interesting... ok, thanks
<mnemoc>
vinifm: please use a paste service supporting line numbers and syntax highlighting next time. http://sprunge.us/ is my favourite
<vinifm>
ok, I also need to study about linux coding style
<traeak>
better than ideone?
<Mehhh>
does anyone have a URL for the a10 mem info
<Mehhh>
so i can wget
<mnemoc>
traeak: by far
<Mehhh>
compiled
<mnemoc>
traeak: defaults to plain text, highlighting is clean and defined on query time, works from command line, it's open source (github) and doesn't try to compile your snippets
<vinifm>
1 more question, in that moment '.probe=some_probe' is named?
bsdfox has quit [Read error: Connection reset by peer]
bsdfox has joined #arm-netbook
bsdfox has joined #arm-netbook
bsdfox has quit [Changing host]
<Mehhh>
Ok, so what is the solution for a10 mem info from a stock android rom
<Mehhh>
wget from busybox isn't cutting it from dling from GH
<hno>
Mehhh, adb push, adb shell
<hno>
is the usual wy
<hno>
way
ol1ver has quit [Quit: ol1ver]
Turl has quit [Excess Flood]
Turl has joined #arm-netbook
voronaam has joined #arm-netbook
<mnemoc>
Mehhh: you'll probably need to chmod +x before adb push. inside android things are more annoying
<Mehhh>
yeh i see that :P
<Mehhh>
screw it i'm just leeching my evb.bin / etc
<Mehhh>
easier to mount from gparted within lubuntu
<Mehhh>
and decomp
<vinifm>
from what I saw when I call i2c_add_driver, it calls .probe, but nothing happens
<mnemoc>
vinifm: there is a #kernelnewbies channel in oftc which might be better for your problems
<vinifm>
ok, thanks :)
Quarx has quit []
freakazoid0223 has joined #arm-netbook
<Mehhh>
errors galore on make tools
<mnemoc>
Mehhh: paste
<Mehhh>
make gcc -g -O0 -Wall -Wextra -std=c99 -D_POSIX_C_SOURCE=200112L -Iinclude/ `pkg-config --cflags libusb-1.0` -o fel fel.c `pkg-config --libs libusb-1.0` Package libusb-1.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `libusb-1.0.pc' to the PKG_CONFIG_PATH environment variable No package 'libusb-1.0' found Package libusb-1.0 was not found in the pkg-config search path. Perhaps you
<mnemoc>
Mehhh: install libusb-dev ;-)
<Mehhh>
That's the thing i have it installed :\
<Mehhh>
I'll manually edit the ENVV and try again
<mnemoc>
at least in ubuntu you need libusb-1.0-0-dev
<mnemoc>
but it's a very distro-specific thing
<Mehhh>
Yeh, the distro i run is ubuntu based so
<Mehhh>
maybe it's a meta issue i'll try that exact spacing
<hno>
Mehhh, what you want to use fel for?
<Mehhh>
I extracted my bins
<Mehhh>
from the nande partition
<Mehhh>
with gparted
<Mehhh>
instead of doing that android adb crap
<Mehhh>
because mk802 ;)
<mnemoc>
hno: as `fel` is built by default in sunxi-tools, you need libusb-dev to build bin2fex and friends too ;-)
<libv>
Mehhh: you only now ran into libusb?
<Mehhh>
I'm just checking the file i submitted from another stick
<Mehhh>
that uses a different name "evb.bin" instead
<Mehhh>
BUt if you want to be an asshole, please continue
<mnemoc>
Mehhh: if your device wants evb.bin, the image was made by a retard.
<Mehhh>
That's why i'm checking it ;)
jquip has quit [Ping timeout: 250 seconds]
<jinzo>
mnemoc, I'm thinking of adding stuff to the comparison table - I'm thinking of link to the product specifications on the Allwinners website and ofcourse a link to the wiki page for this product
<jinzo>
any other wishes?
<mnemoc>
linking the product page is fine. but it's not a real source of information
<mnemoc>
we need to openly provide reliable info
<mnemoc>
and that's not on allwinnertech.com
<jinzo>
ok.
<mnemoc>
jinzo: allwinnertech.com info is very incomplete and unreliable.... they removed the A20 and A10s this morning
<jinzo>
A10s too?
<jinzo>
but supposedly some products shipped with that allready?
<mnemoc>
this morning they prefered the A12
jquip has joined #arm-netbook
<mnemoc>
jinzo: no idea what is on their minds....
<mnemoc>
jinzo: but I'm sure that, if we want to provide reliable information, we need to keep it (and maintain it) ourselves
<Turl>
" ARM System Developer's Guide: Designing and Optimizing System Software (The Morgan Kaufmann Series in Computer Architecture and Design) [Hardcover] " <- this one mnemoc?
<mnemoc>
yes
<Turl>
mnemoc: gdoc link says I need permission
<mnemoc>
Turl: try again
<Turl>
is that pdf public?
ZaEarl_ has joined #arm-netbook
<mnemoc>
you are expected to register on arm.com to download it
<focus_it>
I just find out it be easy to make a BGA chip. Get a foundry to make raw dice, bond to a specially made PCB with very high density wiring and ball grid array pattern, and bob is your uncle! You have a BGA!
<focus_it>
Thats why BGAs are never going to go out of fashion
<focus_it>
Anyone can become a chip shop - just spend 30K to 1M to make your dice and away you go!
<focus_it>
One idea is to find one of the numerous vendors of SoCs out there in CN, get them to port Linux to their SoC and then you got a competitor to ARM at a fraction of the cost - typically $0.60 for a powerful chip.
vinifm has left #arm-netbook ["Saindo"]
<mnemoc>
focus_it: what are you waiting for? ;-)
<focus_it>
mnemoc: I need one of my other projects to make money and then I do it!
<mnemoc>
:)
<focus_it>
I never realize BGAs were just PCB with a diced bonded on top.
<focus_it>
When I was in CN, I used to buy dice and do bonding
<focus_it>
Raw dice is very cheap
<focus_it>
Lead time 9 months to get own CPU made
<focus_it>
At the time, when 8 bits were common, I had offer of a 64 bit on the table
<focus_it>
These companies are desperate for business. They have their own VHDL and can make their own dice in 9 months.
<aholler>
you are forgetting the sw-side.
<focus_it>
Normal 8 bit dice were $0.20. My eyes popped out when they said the 64 bit was $0.60
<mnemoc>
EEs always think that when the hardware is done the project is 98% finished
<focus_it>
aholler: can get them to port Linux to their SoC and then get it released - as I say they are desperate for business and will agree to anything.
<aholler>
haha
<focus_it>
Staff about 20 to 50
<focus_it>
There are numerous and I numerous custom CPU makers out there
<aholler>
beeing desperate for business isn't enough ;)
<jinzo>
or you can buy a cheap MIPS based stuff from ingenic?
<jinzo>
With Android support, cheap prices etc :D
<jinzo>
dunno what the software situation is
<focus_it>
jinzo: need a clean Linux and clean CPU ready for Internet of Things - and cheap preferably
<focus_it>
Then android environment is tied in knots with NDA that kills off every project
<jinzo>
focus_it, that's a bummer, because _everyone_ bundles a GPU with it
<jinzo>
I'm looking at the olimex olinuxino-i233 board (with WiFi)
<jinzo>
and it comes around 50€, then there's 8devices carambola (that's cheaper, 22€ for the bare board)
<focus_it>
jinzo: got link?
<jinzo>
for which one?
<focus_it>
jinzo: most Internet of Things don't need a GPU. And if you make a bundle selling CPU, then you can make your own GPU.
<jinzo>
I have to run and will be be back in 1h or so (and I'm very interested in IoT)
<focus_it>
jinzo: both if you have
<jinzo>
yes exactly
<jinzo>
sorry, have to run
<focus_it>
ok
<jinzo>
brb
freakazoid0223 has quit [Quit: Leaving]
ZaEarl_ has quit [Ping timeout: 244 seconds]
rellla has quit [Quit: rellla]
popolon has joined #arm-netbook
freakazoid0223 has joined #arm-netbook
drachensun has quit [Remote host closed the connection]
<libv>
mnemoc: has something changed recently that should fix the panic when detaching from OTG?
<libv>
anyway, will give it a go once i cracked NPOT textures for lima, so somewhere tomorrow
<jinzo>
focus_it, found it?
<mnemoc>
libv: yes, three fixes went in today
<jinzo>
focus_it, as I'm very interested in low cost IoT that run linux and have WiFi/ZigBee (as mostly for my usage the energy consumption isn't a big problem I prefer WiFi)
<jinzo>
and I'm quite disappointed by the offerings/price (compared to media/tablet/phone SoCs that include a GPU - Allwinner, RK3066, amlogic stuf)
<focus_it>
jinzo: Found the carambola - interesting!
<hno>
jinzo, what is an IoT?
<focus_it>
Internet of Things
<hno>
ah.
<focus_it>
I believe we are imminent cusp of IoT happening soon - not having Linux and cheap SoC holding it all up
<jinzo>
focus_it, yes - it's the only board focused for IoT I found - but there are problems
<focus_it>
hmm.. I got an openwrt board complete with 4 ethernet sockets. Not sure what to do with its limited resources
<aholler>
if you are talking about internet, you'll likely want a maintainable linux, that means upgradable/fixable linux, not just any linux.
<jinzo>
yeah, there're some cheap tp-link routers around that are hackable
<jinzo>
but access to GPIO ports is a bit hard
<jinzo>
btw: there's carambola 2 in the works, but not much info is known (and the company isn't exactly responsive/open as Olimex for example)
<focus_it>
The i.MX233 looks interesting!
<jinzo>
aholler, both those options provide at least some degree of a maintainable distro (and at least carambola is updating it's openwrt tree quite regularly)
<jinzo>
focus_it, yes but it's a bit more expensive as carambola (but on the other hand it depends on what you're doing and in what quantities)
<focus_it>
IoT - my vision is of a generic tablet like internals module with LCD + touch + Linux
<focus_it>
That then has lots of IO pins that can be accessed
<focus_it>
Mainstream Linux should run on the LCD
<focus_it>
So that when users go from room to room operating devices, they are not confronted with something too different from desktop
<jinzo>
bah - I don't need LCD, I just wish a cheap (~20€) device with wifi, linux and some GPIO ports
<jinzo>
for endpoints
<focus_it>
The IoT should be easy to manufacture for $30
<jinzo>
and it's possible - there're even some stuff you can buy for around that price
<focus_it>
The LCD is needed because without it, its hard to make true IoT
<jinzo>
GUIs are overrated :P
<focus_it>
we just end up making hard to control and set up kit
<mnemoc>
GL-based HCIs are nice :p
<mnemoc>
very scifi
<focus_it>
If my fridge had a UI, I would use it to order supplies
<focus_it>
If it didn't I'd be using pen and paper
<focus_it>
pen and paper != IoT
<focus_it>
IoT == LCD + Linux + GPIO pins
<aholler>
jinzo: distro and kernel. and most vendor-kernels are getting only limited support and are often already outdated when the hw becomes available. that might become a problem, especially since ipv6 only now gets used by some more people (and therefor bugs might be found)
<jinzo>
aholler, yes indeed - but fortunately I encountered quite a lot source code only supported SoCs/devices in openwrt
<focus_it>
my reckoning is a tightly bolted down linux with gui and standard desktop distro is what enables IoT
<focus_it>
everything else just redoes what we could do anyway yesterda
<focus_it>
I'd be happy if my soldering iron lit up with temperature graph and a full desktop linux and buttons to set temperature
<jinzo>
hm I have been digging around what happened to Ingenic, the makers of MIPS based XBurst CPU's that made some whirll a year or so aho
<jinzo>
*ago
<focus_it>
being over the top about IoT counts a lot!!
<jinzo>
looks like nothing, they had dual core products on the roadmap for this year
<jinzo>
but they missed that train, too bad.
<jinzo>
I hoped someone will break up the ARM monopoly in this space (and they were ridiculusly cheap)
<focus_it>
The OLED makers are about to go into production with displays printed on continious reels. The prices will drop to $1 or less soon for high resolution colour displays
<jinzo>
if everything goes by the plans. Hopefully :)
<focus_it>
The only way to use all that to make IoT happen is to have extremely cheap ARM (or some other CPU) + full blown desktop Linux and GPIO pins so that developers can get down to making IoT devices on a whim
<focus_it>
I'd be happy if my toaster smiled at me when I walked into a room.
<focus_it>
And offered up a series of toasting options on a touch surface
<jinzo>
a lot of things are needed, but we live in a wonderful time for this sort of things
<focus_it>
IoT is all about technology following you around and helping you out by interacting with you
<focus_it>
Not the dumb things of yesterday
<focus_it>
Highest priority is to get some ARM or other CPU + Linux going
<focus_it>
I am trying to make System on Module board (SoM) that contains A10, flash, SDRAM in KiCAD to release under GPL so that everyone can copy and make their own A10 SoMs.
<aholler>
most things just got more complicated to use than easier to use.
<focus_it>
I release a stepping stone http://www.gplsquared.com/SoM1/SoM1.html that contains dual 100 pin ARM SoM board and motherboard in KiCAD with accurate geometry so that anyone can go make it.
<libv>
dual power connectors?
<libv>
are these 2 SoMs completely detached?
<libv>
err, SoCs?
<focus_it>
Yes for different prototyping
<focus_it>
They are for ARM LPC1764 from NXP
<focus_it>
Good for a lot of things - not Linux though
<focus_it>
The sample serial port program there can also speak through HDMI
<focus_it>
Also you can make it speak by sending it RS232 data with <s> speech text </s>
<focus_it>
So in effect it can talk to you depending on what is going on around you.
<focus_it>
You just make some gadgets and send RS232 strings. Like for example temperature sensor.
<focus_it>
This is the beginnings of the IoT as I see it
hp__ has joined #arm-netbook
<focus_it>
The gambas programs you can develop on your desktop and then move it into the A10+HDMI device the MK802 and it works as well as it does on desktop Linux
<focus_it>
So by using the power of Linux, you got rid of the custom window manager and GUI problems by putting everything down on a biggish but cheapish Linux SoC.
hg_5 has joined #arm-netbook
<focus_it>
The cheaper the SoCs get, the cheaper the SoC + LCD or SoC + HDMI get
<focus_it>
and all running Linux
<focus_it>
and the Linux has access to GPIO pins and RS232, Wifi USB etc to get data in and out
<aholler>
and everythings fights for access to the rs232 ;)
<ManoftheSea>
rs232 is a bad choice. 12V ?
<focus_it>
aholler: sort of - its /dev/tty /dev/USB0 etc
<focus_it>
aholler: this is optically isolated RS232, so no danger with trailing wires everywhere
<aholler>
it's still rs232 with all the common usage problems included.
<focus_it>
IoT has to be very safe
<focus_it>
It can be made to use WiFi and ethernet
<focus_it>
also RS485
<focus_it>
wifi and ethernet require sockets programming
<ManoftheSea>
and allow muxing connections
<focus_it>
RS485 and so on turns up as /dev/... and you just open it
<ManoftheSea>
you can just open /dev/tcp/port... one sce
<ManoftheSea>
/dev/tcp/<ip>/<port>
<focus_it>
ManoftheSea: yes I used to do socket programming but that 15 years ago - so I forget a lot
<mnemoc>
/dev/tcp/<ip>/<port> is a bash thing, unrelated to programming
<aholler>
and then you just read what?
<ManoftheSea>
mnemoc: oh, dang
<focus_it>
aholler: install Gambas on your PC and open the serial port example program (save it somewhere) and see the source code for reading and writing to serial streams
<aholler>
I don't need that
<focus_it>
Its just a couple of lines of code
<aholler>
I wanted to hint that you want to know what you have to read/write, just being able to read/write isn't enough.
<focus_it>
aholler: absolutely, initially every gadget to itself, but I guess people will get up and eventually agree on a standard
<focus_it>
will get fed up and eventually agree on a standard
<focus_it>
I prefer a UUID like idea - but some place where you could obtain a number and deposit its meaning in a context free way so that others can use it
<focus_it>
So you go to some website, and it issues a 64 bit number (for your IoT device and a message that it wants to send), and then you register a text to explain what that number will be used for
<focus_it>
with todays tech - easy enough to set up
<focus_it>
64 bits ought to be enough for anybody (TM)
<focus_it>
aholler: dozens of examples exist. I got many own devices I made as well - all useless unless you got a Linux GUI to do the face to face human interation to make IoT next generation. Otherwise its still out dated yesterday tech