<peterm6881>
yeah thats EXACTLY the kind of steer I was looking for
<Xogium>
but like I said, they are skyrocketting, dongle that used to sell for 20 usd now sell well over 40
<sc6502>
Hey Xogium and peterm6881
<peterm6881>
so is ralink and realtek no good?
<peterm6881>
hey sc6502 welcome :)
<peterm6881>
so, now the gangs all here
<sc6502>
I should stop trying to write C, C++ and Python all at the same time...
<peterm6881>
show off :)))
<peterm6881>
hehe
<Xogium>
heya Steve
<sc6502>
So what's new in hardware land?
<peterm6881>
so, sc6502, you have an idea what we're looking to establish, a means of submitting upstream patches. There wont be any issues, because they will be fully tested, they just need signed off and submitted. Thomas Petazzoni will have the final say on any tweaks required
<peterm6881>
Xogium will explain the nuts and bolts of it
<peterm6881>
over to you guys
<Xogium>
sc6502: mhm are you familiar with the DCO or as it is, developer's certificate of origin ?
<Speedsaver>
Title: Developer Certificate of Origin (at developercertificate.org)
<Xogium>
ahah
<Xogium>
so basically buildroot enforces this, plus having a git commit with a sign-off attached to it
<Xogium>
which requires the full name of the committer
<Xogium>
a bit like linux kernel contribution
<sc6502>
yes
<Xogium>
but disclosing my real name isn't something I am one bit comfortable with
<Xogium>
so we were wondering if you would be willing to submit work I'd have done, as per point (c) of the DCO
<Xogium>
I still have to talk to Thomas Petazzoni about how we would ensure that the work is truly from me and unmodified and all of that, and you would submit with my accord
<Xogium>
but that would be the idea
<Xogium>
that is, if you are comfortable with giving out your real name
<Xogium>
we'd never force you doing it, should you not be willing
<peterm6881>
the end goal is so we can become the official maintainers for anything V3s related that we do, or any other SoC or SiP that we decide to play around with
<peterm6881>
in sbc land, official support is everything
<peterm6881>
as Xogium said, its simply signing off on stuff that Xogium and I have worked on (me in terms of testing), and Xogium has authored
<Xogium>
far as I know the real name must only be present in the signed-off by
<peterm6881>
so we can get it accepted upstream and build the ecosystem
<peterm6881>
By the way I offered, but git is way too complex for me
<sc6502>
Yeah, I should be able to do that.
<peterm6881>
thats a whoop from me
<Xogium>
sc6502: thank you :)
<Xogium>
I'll see about catching Thomas tonight and asking him all questions I can think of about the process
<peterm6881>
sc6502, thanks that's fantastic, thanks from me too
<Xogium>
how do we ensure that my work hasn't been altered, how do they know I give my permission to you, etc.
<peterm6881>
The chap who did the initial work on the Lichee Zero, Michel Stempin, APPEARS to have moved on to other things
<peterm6881>
Its just luck Buildroot havent dropped his defconfig yet
<peterm6881>
so his u-boot is old etc, the build fails for various reasons, but Xogium cured it like a boss
<peterm6881>
quite apart from the value to our little project, I think that deserves to be recognised and adopted upstream
<peterm6881>
any reservations sc6502?
<sc6502>
Presumably it's easy enough for me to review by doing a diff against the previous commits
<Xogium>
yes, I'd assume so
<peterm6881>
perhaps we can test that?
<peterm6881>
with what we've got
<Xogium>
yeah I'm still not clear how I could transfer this to sc6502, so that's also why I wanted to ask Thomas
<sc6502>
So you have local changes from some cloned up-stream repo?
peterm6881 has left #Speedsaver [Leaving]
peterm6881 has joined #Speedsaver
<peterm6881>
oops
<Xogium>
sc6502: yes that's about it
<sc6502>
So if I cloned the same repo, then pulled the delta from your own machine, would that work?
<peterm6881>
Xogium, remind me whats Thomas's nick
<Xogium>
I mean, if they added (c) in the DCO then there must be a way to do this
<peterm6881>
something tom
<Xogium>
peterm6881: kos_tom, but there's no need I already pm him
<Xogium>
he just hasn't responded yet. Probably was at work all day
<peterm6881>
no no i had NO plans to, I was just annoyed I couldnt remember :)
<peterm6881>
i knew it was a greek island
<Xogium>
sc6502: hmmm how would we do this ?
<peterm6881>
maybe invite kos_tom to our channel
<peterm6881>
hes the grand wizard of Buildroot, its his invention
<Speedsaver>
Title: Git - Working with Remotes (at git-scm.com)
<sc6502>
So long as your machine accepts outbound pull requests, I think it's just a matter of adding it as a remote at my end.
<Xogium>
hmm
<Xogium>
and then ameding the commit I made with a SOB ?
<Xogium>
amending
<Xogium>
hmm
<sc6502>
Yeah maybe.
<sc6502>
I'm guessing it'll keep you as committer and me as signed-off by or whatever it is
<sc6502>
Can't stop too long, got a 5am start tomorrow
<Xogium>
that is okay :) how about for tonight I try and catch Thomas and see what he says, and tomorrow or the day after, we meet here again and we set things up like he'll have suggested ?
<Xogium>
does that sound good ?
<peterm6881>
make it so ;)
<sc6502>
Sounds good to me - Friday evening. I won't be back tomorrow until late.
<Xogium>
alright, lets try that then
<peterm6881>
what time works for you guys?
<peterm6881>
best development is the heavy kind
<peterm6881>
Elvis has left the building
<Xogium>
time doesn't matter much for me
<Xogium>
think you know already
<peterm6881>
the good thing is its logged!
<peterm6881>
i found an interesting thing just now
<Xogium>
what's that ?
<peterm6881>
i was looking on ebay for MediaTek usb wifi dongles
<peterm6881>
I found one that in the description it says the following
<peterm6881>
Mediatek/Ralink 7601/5370 chipset
<peterm6881>
I used to have dozens of Ralink dongles, they were great
<Xogium>
sounds like they are not sure which chipset it is
<peterm6881>
i think maybe its the same chip
<peterm6881>
might just have a different ID
<peterm6881>
depending on whos selling it
<peterm6881>
USB WiFi Dongle Kali Linux Compatible Hacking Wireless Networks Compact Size
<peterm6881>
whats Kali, any idea?
<peterm6881>
pen testing and ethical hacking.....
<Xogium>
oh, its a weird debian derivative apparently focused on security and hacking
<peterm6881>
precisely
<peterm6881>
Ralink Technology logo.svg
<peterm6881>
FoundedJanuary 2001, Cupertino, CA
<peterm6881>
IndustrySemiconductor
<peterm6881>
HeadquartersHsinchu, Taiwan
<peterm6881>
TypeSubsidiary
<peterm6881>
ProductsWi-Fi chipset
<peterm6881>
ParentMediaTek
<peterm6881>
Websitenone
<peterm6881>
MediaTek owns Ralink
<peterm6881>
hmm.......I need some of those
<peterm6881>
you have a MediaTek or Ralink usb wifi dongle thats fully supported?
<peterm6881>
Linux
<peterm6881>
require a firmware to be loaded. Ralink allows the use and redistribution of firmware, but does not allow its modification.
<peterm6881>
Drivers for MediaTek Ralink wireless network interface controllers were mainlined into the Linux kernel version 2.6.24. (See Comparison of open-source wireless drivers.) Ralink provides GNU General Public License-licensed (GPL) drivers for the Linux kernel. While Linux drivers for the older RT2500 chipsets are no longer updated by Ralink, these are now being maintained by Serialmonkey's rt2x00 project. Current Ralink chipsets
<peterm6881>
In February 2011 Greg Kroah-Hartman praised Ralink for their change in attitude towards the Linux kernel developer community:
<peterm6881>
As you can see in these posts, Ralink is sending patches for the upstream rt2x00 driver for their new chipsets, and not just dumping a huge, stand-alone tarball driver on the community, as they have done in the past. This shows a huge willingness to learn how to deal with the kernel community, and they should be strongly encouraged and praised for this major change in attitude.
<peterm6881>
— Greg Kroah-Hartman on 2011-02-09, here
<peterm6881>
Ralink chipsets require a firmware to be loaded
<peterm6881>
one assumes MediaTek, umm... dont
<Xogium>
I was lucky enough that the realtek dongles you sent me work, but they do only work with an external kernel module. They are not mainline, and probably never will be, like most realtek
<Xogium>
oh, they could well require a firmware. But the firmware and driver should both be upstream
<peterm6881>
im gonna try a couple of those RT5370 nano dongles
<peterm6881>
maybe we can see if we can get wps working
<Xogium>
yeah, maybe…
<peterm6881>
you said its turned off on your router?
<Xogium>
yeah, big security hole
<Xogium>
in the case of that router at least
<peterm6881>
presumably you can switch it on and off at will, for testing?
<peterm6881>
This nano WiFi dongle utilises the Ralink 5370 Chipset. Its sold by a company we used to buy USB touchscreens from in a previous job
<peterm6881>
so they're legit
<peterm6881>
New IT
<peterm6881>
they're aiming them at RPi owners
<Xogium>
should be able to but I reckon enabling networking in the kernel plus the driver we'll need will slow down the boot even more :p bigger kernel
<peterm6881>
ok ive bought 2
<peterm6881>
boot time doesnt matter for this use case
<peterm6881>
its just a fun demo if you like, especially since the MangoPi-R3c has a direct speaker output
<Xogium>
well, still… a minute between power up and demo starting, daresay it risk not impressing many folks
<peterm6881>
yeah that would be cool, runnning off the SPI Flash
<Xogium>
not to mention that the only people who'll be able to use this board are buildroot experts
<peterm6881>
its fine we can explain its a limitation of spi flash, especially non QSPI
<peterm6881>
if they weant faster boot, grab an SD card
<peterm6881>
want *
<peterm6881>
we can use the same jingle ;) so they know its booted
<peterm6881>
hehe
<peterm6881>
since the board has no useful leds
<peterm6881>
as a homage to its parent project
<peterm6881>
yeah lets do this
<peterm6881>
ill get the website set up and start generating revenue
<peterm6881>
i have a question for you
<peterm6881>
Buildroot is its natural habitat, but do you think this board COULD run something else?
<peterm6881>
from the Micro SD card
<peterm6881>
is it enough ram to run Armbian?
<peterm6881>
you're mates with Igor ;)
<Xogium>
given that armbian doesn't support armv5 devices, probably not
<peterm6881>
grrr
<peterm6881>
dropped it or never did?
<Xogium>
looks like base armbian is also quite ram hungry
<Xogium>
total
<Xogium>
Mem: 3.7Gi 143Mi 39Mi 4.0Mi 3.5Gi 3.5Gi
<Xogium>
woops that first line badly copied itself but
<peterm6881>
Depending on the architecture, it is possible to install Debian with as little as 20MB (for s390) to 60MB (for amd64)
<Xogium>
I don't think they ever supported armv5
<peterm6881>
what have u got running armbian?
<Xogium>
awnd, even if they did, mainline debian is struggling more and more with armv5 and considering dropping it
<Xogium>
*and
<peterm6881>
alright, we focus on Buildroot then
<peterm6881>
its enough
<Xogium>
I run armbian on odroid hc4 for the armbian mirror
<Xogium>
rather, I just bought the board, put it online with a vpn access, and left the armbian folks do whatever they pleased with it to setup the mirror
<Xogium>
or… nah, I more or less just received the board, given that Igor payed for it. True that, almost forgot
<Xogium>
jesus it beats my phoenix in terms of uptime