jstein has quit [Remote host closed the connection]
florianH has quit [Quit: Connection closed for inactivity]
bugzc has joined #linux-sunxi
honx has quit [Ping timeout: 252 seconds]
marvs has quit [Ping timeout: 260 seconds]
honx has joined #linux-sunxi
marvs has joined #linux-sunxi
nashpa has quit [Ping timeout: 244 seconds]
nashpa has joined #linux-sunxi
BuddyZhang1 has quit [Quit: Page closed]
tlwoerner_ is now known as tlwoerner
Ntemis has quit [Remote host closed the connection]
dlan has joined #linux-sunxi
<victhor>
hi, I'm taking a look at this "Aoson M751s" tablet board, from the wiki it says there is no UART found on the board. I wonder if anyone with one of these managed to find one on those pads on the bottom of the board, and the wiki's just not updated... I went through them with a oscilloscope, I found a lot of pins at 3.3V, but no activity, and some pins, which would show some activity when the power button is pushed, but it's a 5V signal, and those
<victhor>
pins would not respond to echo to the serial ports, and I could not decode the signal with my USB-serial adapter.
<victhor>
I guess I'm out of luck and my only choice for debugging is to plug the LCD in?
cnxsoft has joined #linux-sunxi
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
terra854 has joined #linux-sunxi
chomwitt has quit [Ping timeout: 256 seconds]
muvlon_ has joined #linux-sunxi
muvlon has quit [Ping timeout: 258 seconds]
ninolein has quit [Ping timeout: 258 seconds]
ninolein has joined #linux-sunxi
kaspter has joined #linux-sunxi
BuddyZhang1 has joined #linux-sunxi
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
<wens>
victhor: it's possible that the pin isn't muxed to uart, so you don't get any traffic
yann-kaelig has quit [Quit: Leaving]
<victhor>
hmm, right
<victhor>
since u-boot and kernel work, I could try changing parameters on the device tree... it's quite annoying to not be able to interact with the device, short of using a keyboard, but I don't have any spare :/
<wens>
victhor: u-boot doesn't look at the devicetree
<wens>
iirc the default is to not use the microSD pins for UART
<victhor>
right
Andy-D has joined #linux-sunxi
victhor has quit [Read error: Connection reset by peer]
marvs has quit [Ping timeout: 260 seconds]
marvs has joined #linux-sunxi
leviathanch has joined #linux-sunxi
leviathanch has quit [Read error: Connection reset by peer]
leviathanch has joined #linux-sunxi
orly_owl has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
kaspter has quit [Ping timeout: 250 seconds]
foxx_ has joined #linux-sunxi
pg12 has quit [Ping timeout: 260 seconds]
pg12 has joined #linux-sunxi
IgorPec has joined #linux-sunxi
Putti has quit [Quit: Leaving]
JohnDoe_71Rus has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
TheSeven has quit [Ping timeout: 260 seconds]
[7] has joined #linux-sunxi
Putti has joined #linux-sunxi
Putti has quit [Ping timeout: 245 seconds]
jernej has joined #linux-sunxi
reinforce has joined #linux-sunxi
f0xx has joined #linux-sunxi
foxx_ has quit [Remote host closed the connection]
IgorPec has quit [Ping timeout: 240 seconds]
scream has joined #linux-sunxi
<MoeIcenowy>
jernej: is your HDMI register addresses obfuscated now?
<wens>
got my bpi m2 ultra
sunxi_fan1 has joined #linux-sunxi
<MoeIcenowy>
jernej: your new commit works well on Orange Pi One.
<jernej>
MoeIcenowy: They were always obfuscated
<jernej>
thanks for testing
<jernej>
This obfuscation thing is something I wanted to ask in RFC
<ssvb>
wens: you can find the BROM address by checking the V bit in SCTRL
<ssvb>
I think you suggested before that we can get the SoC ID from the BROM header
florianH has joined #linux-sunxi
<wens>
given that the BROM is only in 1 of 2 locations, and has a distinguishing header, should be easy to check
f0xx has quit [Quit: terminated!]
diego_r has joined #linux-sunxi
massi has joined #linux-sunxi
BuddyZhang1 has quit [Ping timeout: 260 seconds]
f0xx has joined #linux-sunxi
f0xx has quit [Ping timeout: 248 seconds]
<wens>
interesting, the bsp still has a fex file
<MoeIcenowy>
wens: it's a stub, contains only some flashing parameters
tuxillo has quit [Remote host closed the connection]
<wens>
dram controller might be the same as the h3
<wens>
nope, looks like the a64
yann has joined #linux-sunxi
<ssvb>
wens: does it work?
<ssvb>
I mean the a64 dram init code
<wens>
ssvb: haven't tried it yet
Worf has joined #linux-sunxi
Worf has quit [Quit: Konversation terminated!]
leviathanch has quit [Remote host closed the connection]
Worf has joined #linux-sunxi
fkluknav has joined #linux-sunxi
LargePrime has quit [Ping timeout: 256 seconds]
kotky has joined #linux-sunxi
f0xx has joined #linux-sunxi
tkaiser has joined #linux-sunxi
<tkaiser>
wens: Any specific reason why you wrote DRAM clocked @ 672 MHz and CPU at 1.0 GHz to the BPi M2 Ultra page?
<wens>
tkaiser: it's the default setting from their dts file
<MoeIcenowy>
Lichee Pi guys are going to make an A33 board and *a V3s board*
<tkaiser>
wens: Hmm... CPU cores are there allowed to clock with 1200 MHz. And based on the 'budget cooling' settings DRAM will be clocked with 576 MHz max currently
<tkaiser>
wens: DRAM seems ok to me but IMO we should change 1.0 GHz to 1.2 GHz on the wiki page.
<tkaiser>
wens: When looking through the various settings it seems that Allwinner is pretty aware of thermal issues (also GPU throttling). But I believe that's due to R40 being also a V40 and T3 (automotive use, GPU and video engine)
<MoeIcenowy>
V series is used for cameras
<tkaiser>
MoeIcenowy: But you can't compares V40 with V3/V3s (based on product brief)
<MoeIcenowy>
yes... maybe V40 is for higher usage
<tkaiser>
BTW: V40 product brief mentions EMAC+EMAC while those of R40 and T3 say GMAC+EMAC -- everything else seems to be the same as R40
<wens>
tkaiser: the A31 manual also uses EMAC instead of GMAC
<tkaiser>
wens: Ok, and that's not even a 'manual' but a 'product brief' so why bother anyway :)
<wens>
tkaiser: my point was they use the terms interchangeably :)
<tkaiser>
wens: I know but I fear the marketing folks responsible for product briefs have no idea regarding the meaning of all those 4 letter words anyway ;) So they use what looks reasonable (more or less)
popolon has joined #linux-sunxi
<tkaiser>
wens: A decade ago I wrote an article for an IT magazine about ZeroConf and Multicast DNS. The copy editor then did a last-minute replacement of all 'mDNS' occurences with 'DNS' -- that was fun since this version went to press :)
<wens>
:|
<tkaiser>
wens: Another question: Did they gave you a battery too? AFAIK no schematics are released for the M2 Ultra so no one knows whether a SATA disk would be powered when running on battery or not.
<wens>
nope
<wens>
i'm quite sure i can't buy one from taobao though
<wens>
something about couriers not liking li-ion batteries
<tkaiser>
wens: ok, then lets wait until schematics are released. Hope it's faster than with Lamobo R1 (took them almost one year) ;)
<wens>
ok, got my opi pc plus working (needed to fetch the mac address)
<wens>
they changed the polarity of the network leds :|
muvlon_ has quit [Quit: Leaving]
<wens>
i think one of my h3 boards is screwing with my ethernet switch...
<dgp>
Getting JTAG going on the orange pi zero was easier than I thought it would be :)
<mripard>
dgp: if you could document that on the wiki somewhere, that would be great
<dgp>
Was just thinking that
<MoeIcenowy>
dgp: you used MicroSD Breakout?
<dgp>
MoeIcenowy: no, JTAG pins on the two row header
<dgp>
OpenOCD can see the target but can't do anything with GDB yet
mcan_ has quit [Quit: by]
victhor has joined #linux-sunxi
lkcl has quit [Read error: Connection reset by peer]
lemonzest has joined #linux-sunxi
lkcl has joined #linux-sunxi
chomwitt has joined #linux-sunxi
Da_Coynul has joined #linux-sunxi
Da_Coynul has quit [Client Quit]
Nacho has quit [Remote host closed the connection]
<terra854>
Hey guys, did anyone got hold of the NES Classic?
<terra854>
edition
Nacho has joined #linux-sunxi
<jelle>
someone posted a u-boot patch
<MoeIcenowy>
mripard: do you know who's working on A13/R8 CSI?
Pepe has joined #linux-sunxi
<mripard>
I am, but with a low priority
<MoeIcenowy>
mripard: have you made any progress?
ldearquer has quit [Remote host closed the connection]
f0xx has quit [Quit: terminated!]
f0xx has joined #linux-sunxi
<MoeIcenowy>
mripard: another question, is anyone working on porting axp288-xx drivers to axp20x generic?
<mripard>
I haven't made any progress since september or so
<MoeIcenowy>
may I do it :-)
<mripard>
and I'm not sure what your question about the axp288 is
<MoeIcenowy>
I just do not want to duplicate work
<MoeIcenowy>
there's many drivers named axp288-xxx in kernel now, which is written by Intel
<MoeIcenowy>
is there anyone working on make them not axp288-specified but axp20x-generic?
tuxillo has joined #linux-sunxi
tuxillo has quit [Client Quit]
tuxillo has joined #linux-sunxi
<mripard>
not as far as I'm aware
<MoeIcenowy>
I think I may do it :-)
<mripard>
go ahead
<mripard>
I think doesn't care now it's upstream
<wens>
intel seems to have abandoned them :(
<scelestic>
absolutely unrelated to sunxi but as a debian user since 2.x i just developed some serious hate towards systemd (yes i've been living underneath a rock for some time0
<mripard>
and we don't really either since it's not really sunxi related
<MoeIcenowy>
wens: someone give them back to life
<mripard>
so I you feel like it, then it's definitely something worth doing
<wens>
MoeIcenowy: if you want to, go ahead. I don't have hardware for it
<wens>
having my name pop up as maintainer doesn't help :|
<MoeIcenowy>
wens: I do not mean doing anything AXP288-related
<MoeIcenowy>
but make the drivers working for axp209 and 223
<MoeIcenowy>
you at least will care axp223, right?
<wens>
yes
<mripard>
MoeIcenowy: qschulz has been working on an ADC driver for the 209 / 223
<mripard>
and on the battery support as well
<MoeIcenowy>
I see nothing in his github
<mripard>
he was planning on submitting his patches this week or the next
<MoeIcenowy>
oh got a WIP patch
<wens>
MoeIcenowy: not everyone pushes to github :)
<wens>
mripard: i think the main headache point is that a lot of the pin functions are very generic and flexible
<MoeIcenowy>
wens: yes I sometimes also forgot to push
tsuggs has quit [Remote host closed the connection]
<mripard>
wens: he also did a pinctrl driver
<MoeIcenowy>
but I think qschulz cannot get his patch merged, since there's already axp288-adc and axp288-fuel-gauge :-(
<wens>
for example the battery temp. sensor can also be used as an ADC
<wens>
and the charging LED can be used like an output GPIO
<wens>
MoeIcenowy: honestly, i don't care about axp288
<MoeIcenowy>
yes
<MoeIcenowy>
but I think at least some kernel maintainers won't allow two similar drivers to exis
<MoeIcenowy>
exist
<wens>
i would like someone to at least look into whether the 2 axp288 drivers can be reused
<MoeIcenowy>
I'm trying to modify axp288-adc to axp20x-adc
<wens>
if not, why? is it a mismatch with the split of functions for what we have planned for the axp20x drivers?
<MoeIcenowy>
what's planned?
<wens>
well, we already have usb-power-supply and gpio
<hramrach>
it seems the axp288 functions are hooked into axp20x already
<wens>
acin-power-supply is just a copy of usb-power-supply away
<hramrach>
it's just not other chip revision has support for that function
<MoeIcenowy>
and I do not like the axp288-charger driver
<mripard>
wens: and he did acin too
<MoeIcenowy>
it's a mixture of usb and acin
<wens>
and who knows how those 2 are supposed to interact with the battery charger driver
<wens>
mripard: cool
<MoeIcenowy>
so axp288-charger, at lesat, won't be used by me
<hramrach>
it depends on chip revision :/
<MoeIcenowy>
reused *
<MoeIcenowy>
but fuel-gauge may be reused
<hramrach>
some are more featureful than others with regards to possible use of acin/usbin/battery
<wens>
hramrach: what chip revision?
<hramrach>
axp152/axp209/whatever
<hramrach>
I don't reacall exact details but looked at the registers once and there were some which you would think there must be to make sane use of the PMIC .. bu sometimes they were missing
<hramrach>
like registers telling you which power source you are on
<wens>
they are the same family
<hramrach>
or at least they were not documented well enough
deskwizard has joined #linux-sunxi
bmeneg has quit [Ping timeout: 260 seconds]
bmeneg has joined #linux-sunxi
<willmore>
What was wrong with "Lemon pi"? It's my favorite kind of pi. Mmmm.....
<KotCzarny>
allwinner based one shouldnt be much harder
<KotCzarny>
see opi0
<willmore>
It's a two layer board with high speed data, low speed data, low level RF, high level RF, and a need to isolate all of them and their separate power runs.
<willmore>
I like my Opi Z. I keep thinking it would be better with no ethernet.
<mripard>
MoeIcenowy: and for the camera, I had most of the driver written
<mripard>
I was able to capture some frames
<mripard>
at the right size
mcan_ has joined #linux-sunxi
<mripard>
but the image itself wasn't good
<mripard>
I have to setup a board to boot with 3.4 and compare
<jelle>
nice!
<ErwinH>
Why is the root account not locked out after creating a user account?
<MoeIcenowy>
ErwinH: it's a distro-related problem
<MoeIcenowy>
please ask it with your distro
<jelly>
(and it's not a problem at all, root account is independent of normal user accounts)
<ErwinH>
Mea culpa!
yann-kaelig has joined #linux-sunxi
<hramrach>
hm, USB3
<hramrach>
what chip is that S500 Lemon Pi uses?
DullTube has quit [Quit: Leaving]
<willmore>
KotCzarny, google "creamy lemon". Do it. :)
<KotCzarny>
not going to
<KotCzarny>
food time ;)
<willmore>
I get a screen full of recipies.
<willmore>
Most of them sound good.
afaerber has joined #linux-sunxi
<willmore>
No anime at all. even the suggestions are all for different recipies. Maybe google knows me too well? ;)
<hramrach>
google's self-censorship is sometimes subtle and sometimes very blatant when you compare results with competition
<hramrach>
I have no idea if it applies in this case, though
cnxsoft has quit [Quit: cnxsoft]
afaerber has quit [Ping timeout: 260 seconds]
afaerber has joined #linux-sunxi
f0xx has quit [Ping timeout: 248 seconds]
Jacmet has quit [Ping timeout: 260 seconds]
Jacmet has joined #linux-sunxi
<tuxillo>
NiteHawk: thanks
Worf has quit [Quit: Konversation terminated!]
hojnikb has joined #linux-sunxi
<hojnikb>
anyone figured out how to change hdmi resolution on h5 ?
<KotCzarny>
the same as for any other h3 legacy kernel?
<hojnikb>
nope
<hojnikb>
its aarch64
<hramrach>
so does it have script.bin?
<MoeIcenowy>
no
<hramrach>
does it have fbdev?
<NiteHawk>
tuxillo: if you encounter any problems on Dragonfly, let me know - but the patch seemed pretty "natural", so i finally merged it
<hramrach>
does it have simplefb?
<hojnikb>
no idea
<hojnikb>
i'm running ubuntu image from xunlong site
<tuxillo>
NiteHawk: yeah, it built on dragonfly. there are a couple warnings about usleep and getimeofday
<hramrach>
then look in /sys to get some idea
<tuxillo>
related to the posix chosen for the build
<tuxillo>
but that's not so important :)
<tuxillo>
and they were there since I tried the first time
tkaiser has joined #linux-sunxi
<NiteHawk>
tuxillo: yes, i'm seeing those too on windows builds, but apparently they're not breaking anything important :D
<tkaiser>
hojnikb: As the one who released the OS image you use. They currently rely on Allwinner's BSP so for every little bit of changed stuff you need to overwrite large portions of the image's start. In other words: Try to find someone as brave as longsleep back then who did the dirty work to clean up A64 BSP for H5 now. Until this is resolved not that much will happen anyway.
<NiteHawk>
btw: wens, thanks for the R40 and A80 patches
<hojnikb>
tkaiser: i see
<hojnikb>
well at least board is somewhat useful
<longsleep>
tkaiser: i might do it again when they release a 2GB version and mainline situation does not suit my needs then :)
<tkaiser>
hojnikb: Allwinner BSP issues aren't that on-topic here either. Your only chance at the moment is to check out that H5 'SDK' and try your luck. Awful experience anyway.
<tkaiser>
longsleep: In case you want an OPi 3 sample, just ask IgorPec ;)
<hojnikb>
tkaiser: i think i'll skip that :)
<hojnikb>
besides my little h3 boards are plenty useful now that armbian support is somewhat mature
<longsleep>
tkaiser: OPi3 is what exactly?
<hojnikb>
orangepi 2e with h5 i'm guessing
<tkaiser>
hojnikb: Then simply sit and wait until someone did the work. I really don't understand why people buy new hardware and expect it should work as mature hardware.
<hojnikb>
tkaiser: obviously nobody expects thats, especially not from chinese vendors
<tkaiser>
longsleep: H5 with 2 GB DRAM and a bit larger. And the same Wi-Fi/BT combo as Pine64 uses
<tkaiser>
longsleep: In other words, Pine64 in better quality and A64 exchanged with H5 (and 2 more real USB ports) ;)
<tkaiser>
longsleep: Half the size
<hojnikb>
yeah whats up with the huge size of pine64
<wens>
looks like the r40's pio is compatible with the a20
<longsleep>
tkaiser: sounds almost useful :) is the wifi optional?
reinforce has quit [Quit: Leaving.]
<hojnikb>
any tests of r40 sata speed ?
<hojnikb>
is it still the same crappy implementation as a20 ?
<MoeIcenowy>
wens: I think for R40 there's also libdram, right?
<wens>
MoeIcenowy: there are sources, which seems the same as a64
<tkaiser>
longsleep: I've only seen pictures, it's onboard. But I don't know much about it since not released. Just a 'leak' some weeks ago.
<MoeIcenowy>
sources?!
<wens>
MoeIcenowy: see the bsp
<longsleep>
tkaiser: all right, lets wait for more details then :)
<tkaiser>
longsleep: I would believe Xunlong just waits a bit so in case you want to have a look asking Igor is the best idea (he's in touch with Steven on a regular basis)
<NiteHawk>
tuxillo: might also be related to compiler version, i think Travis is a bit conservative there (gcc 4.x)
<hojnikb>
is xunlong affiliated with allwinner in any way ?
<hojnikb>
everything they put out is based on their hw
<wens>
very nice, r40 pinctrl is completely the same as a20
<wens>
only new stuff is the I/O disabled state, which we don't care about
<wens>
looking at the code is easier, and has more info
<MoeIcenowy>
do R40 have a CPUs ?
<wens>
don't think so
<wens>
no secure sram either
clonak has joined #linux-sunxi
<wens>
hmm, maybe it does, but the bsp doesn't exactly scream it
<MoeIcenowy>
it's really an A20 with some IP block updates :-)
<wens>
which makes it extra tricky to work into the existing u-boot structure
<hojnikb>
looking at the their product portfolio (allwinner sure has a lot of stuf) i'm guessing they only really make 2 or 3 dies and fuse off stuff that a particular segment doesn't need. For example h3 and v3 seem very similar, even though they are mean for completly different market.
<MoeIcenowy>
hojnikb: ARE YOU SURE THAT H3 IS SIMILAR TO V3?
<KotCzarny>
wens: maybe there shouldnt be socs categories, only IP blocks autodetect routine
<wens>
KotCzarny: we're kind of past that :p
<hojnikb>
MoeIcenowy: well both use a7 and mali 400
<MoeIcenowy>
V3 is single-core
<hojnikb>
you can disable 3 cores
<KotCzarny>
wens: code refactoring, ahoy!
<wens>
hojnikb: so does half of allwinner's products :p
<hojnikb>
wens: thats why i'm suspecting that they only design a few dies and just disable stuff that doesn't work or is not needed
<wens>
hojnikb: but they don't tell you this :p
<hojnikb>
wens: obviously not
<hojnikb>
but if this is true, this would mean possibility to unlock certain ip blocks. Unless they are laser cut.
<MoeIcenowy>
I now doubt that the known whole T series are all renamed SoCs.
<MoeIcenowy>
T2 - A20, T3 - R40, T8 - A83T
<mripard>
hojnikb: usually, the pins are simply not routed
<MoeIcenowy>
mripard: I now believe A13 is the same as R8
<MoeIcenowy>
someone made a board that uses A13's TVout
<MoeIcenowy>
and it's tested
<mripard>
who ?
<MoeIcenowy>
the "Lichee Pi" I said this afternoon in UTC+8
<KotCzarny>
otherwise most of the device pages are horribly outdated
<MoeIcenowy>
KotCzarny: soon we may need support to V3s
<MoeIcenowy>
V3{,s} is Single-Core Cortex-A7
<MoeIcenowy>
designed for cameras and (ab)used by Zepan for Lichee Pi Zero
<jelle>
but you like the abuse, right?
f0xx has quit [Ping timeout: 258 seconds]
<NiteHawk>
KotCzarny: may still be somewhat relevant for the (3.4) BSP kernels - but yes, mainline tends to get outdated quickly. maybe adjust the ND template accordingly... libv?
<KotCzarny>
nitehawk: and what's worst, people see device page, see a13, see 'unsupported' and leave
<KotCzarny>
anyone can paste mainline status link into 'status' paragraph?
silviop has quit [Remote host closed the connection]
<miasma>
hm the soc pages are probably a bit outdated too. e.g. on the H3 SoC page "Currently, there is no sunxi support available yet. SDK has been released in May-2015, and devices are slowly becoming available."
<MoeIcenowy>
I think for some SoC I should do "citation needed"
<MoeIcenowy>
e.g. R18
<MoeIcenowy>
R18 never exists on allwinnertech.com...
<MoeIcenowy>
and allwinner seems to made newer F-series SoCs..
<MoeIcenowy>
renewer many references on Allwinner_SoC_Family
<tuxillo>
besides this pine64, are there more armv8 boards?
<tuxillo>
SoCs
<KotCzarny>
a64, h5
<tuxillo>
like which one?
<MoeIcenowy>
SoC: H5
<MoeIcenowy>
in Orange Pi PC2
<tuxillo>
ok
<MoeIcenowy>
Banana Pi M64 is also A64-based
<tuxillo>
worth buying?
<MoeIcenowy>
how to show SoC rename on Allwinner_SoC_Family is also a problem...
<KotCzarny>
never buy bananas
<tuxillo>
you know, my drawers are empty :)
<KotCzarny>
pine64 is better
<KotCzarny>
and you can wait for more oranges if you need more ram
<KotCzarny>
MoeIcenowy: redirect page
<KotCzarny>
or add as notes under table
<MoeIcenowy>
I will do some try on R8/A13 pair
<terra854>
Was hoping Allwinner made a SoC with 8 core arm64 and a better Mali GPU
<terra854>
and not using the crappy Mali 4xx
<terra854>
and outdated
<wens>
terra854: you'll probably have better luck with mediatek or rockchip?
<MoeIcenowy>
do not try mediatek
<MoeIcenowy>
they're covered with heavy NDA
<tuxillo>
hmm, I thought ODROIDs had Allwinner
<MoeIcenowy>
As OtakuNekoP said, Banana Pi R2 used a MediaTek SoC, and a lot of the price of R2 is for the document fee
<terra854>
ODROIDs have exynos
<MoeIcenowy>
s/document/SDK
<terra854>
and amlogic
<MoeIcenowy>
MediaTek SDK is even difficult to retrieve
<libv>
miasma: that is so because nothing related to c.h.i.p. ever seeps back into the wiki.
tkaiser has quit [Read error: No route to host]
tkaiser has joined #linux-sunxi
<tuxillo>
so besides the pine64 what else would you recommend?
<KotCzarny>
opipc2, but h5 is not yet supported, so might take a while
<tkaiser>
MoeIcenowy: First Pine64 prototypes were made with R18 and SinoVoip also did a few BPi M3 with R58 and H8 instead.
<MoeIcenowy>
tkaiser: yes... do you have the link to the Pine64 prototypes now?
<tuxillo>
orange pi pc2 from aliexpress 22eur, comes with H5
<tuxillo>
and yeah, 1GB
gnufan has joined #linux-sunxi
<MoeIcenowy>
and there's also a problem for slightly different SoCs
<MoeIcenowy>
for example, A64/H64, H3/H2+
<tuxillo>
what is it
<MoeIcenowy>
I'm talking about the wifi
<MoeIcenowy>
wiki *
<tuxillo>
ah
<tuxillo>
:)
<MoeIcenowy>
I created a redirect from R16 to A33, R8 to A13
<KotCzarny>
you should also a note on a13/a33 pages if they dont have one regarding R version
<MoeIcenowy>
KotCzarny: note added
<MoeIcenowy>
and added R8/R16 devices categories' show to A13/33 pages
<MoeIcenowy>
now... should we merge H64 and A64, merge H2+( not exist now) and H3 ?
<MoeIcenowy>
they're proven to have the same SoC ID, but slight differences
<tkaiser>
MoeIcenowy: H64 is dead. And H2+ slightly different.
<MoeIcenowy>
tkaiser: there's many dead SoCs on our wiki :-)
<tkaiser>
What about an own page for H2+ that just outlines the differences and then contains a link to H3 page? Same with H64
<MoeIcenowy>
OK
<KotCzarny>
tkaiser, why not just a paragraph on h3 page?
<MoeIcenowy>
yes it's a problem
<tkaiser>
I'm fine with that but OPi Zero page already links to a H2+ page. We could add a 'variants' section on the 'main' SoC pages and the link to the anchor?
<tkaiser>
So H2+ is a link to [[H3|#Variants]]
<MoeIcenowy>
we can make redirections
<KotCzarny>
its like cataloguing 'products' made from lego bricks
<tkaiser>
Can a redirect also target an anchor? H2+ is a redirect to [[H3|H2+]]?
<MoeIcenowy>
I think it's available on Wikipedia
<MoeIcenowy>
and I think for one SoC allwinner have 3 kind of IDs
<MoeIcenowy>
we cared most on product names (A33, A64)
<MoeIcenowy>
then on sequence id (sun8iw5, sun50iw1)
<MoeIcenowy>
but we nearly ignored the develoment code (aster, tulip)
<KotCzarny>
fruits made from flowers
<MoeIcenowy>
and from Tina SDK we proved that R16 comes with the same development code with A33 (aster)
<MoeIcenowy>
The development code usually is also the start of "Build Number" in stock Android
LargePrime has quit [Ping timeout: 265 seconds]
<yann-kaelig>
Hi. This is not really clear for me on the sunxi wiki, but can I use the sunxi-next branch to get the 3D graphics and playback acceleration ?
<MoeIcenowy>
yann-kaelig: no.
lemonzest has quit [Quit: Leaving]
<yann-kaelig>
Arf. There is no way to get 3D graphics and acceleration instead the old sunxi-3.4 branch ?
<KotCzarny>
heh, files in lichee/tools/daily_build/ contain plain email addresses if anyone wants to spam allwinner guys
<MoeIcenowy>
KotCzarny: ;-)
KB3VGW has joined #linux-sunxi
<MoeIcenowy>
but I think at least one of the mail addresses are not available ;-)
LargePrime has joined #linux-sunxi
<yann-kaelig>
Why is there no up-to-date of 3D graphics and acceleration with newer kernel, at least on the longterm 4.4.x kernel version ?
<KotCzarny>
because licenses
<KotCzarny>
and moneys
<yann-kaelig>
really, the licence close the use on a specific kernel ?
<KotCzarny>
licence closes use on any kernel if its not permissive/unknown
jstein_ has joined #linux-sunxi
deskwizard has quit [Ping timeout: 248 seconds]
jstein_ is now known as jstein
<MoeIcenowy>
to be honest there's 3d support for some forked 4.x
<MoeIcenowy>
using blobs from NextThingCo
<yann-kaelig>
that really strange for me this sort of licence. that mean all the work who has done in the past is for ever lost
<wens>
yann-kaelig: the license is for the vendor, not the community
leviathanch has quit [Read error: Connection reset by peer]
ldearquer has joined #linux-sunxi
leviathanch has joined #linux-sunxi
tkaiser has joined #linux-sunxi
<willmore>
scelestic, PowerVR graphics on a chip? Cool, then noone will have to worry about if it'll get 3D graphics support! The answer will be a solid "no". That makes things a lot easier.
<willmore>
KotCzarny, aren't all fruits made from flowers?
<KotCzarny>
willmore: what about fruits of the loins?
<willmore>
You going to name boards off of my children?
<willmore>
Can we use their nicknames? That'd be cool. :)
paulk-collins has joined #linux-sunxi
<KotCzarny>
tbh, child pi could be cool marketing name
<KotCzarny>
or kid pi
<willmore>
Moo pi and Bear pi. That'll work.
<willmore>
Moo pi might be taken badly in English speaking countries.
<willmore>
Bear pi just sounds confusing. Is it pie made from a bear? Is it a pie for a bear? Is it a spherical bear with uniform density?
<KotCzarny>
or a pi board fitting in a beer
<willmore>
Beer pi?
<KotCzarny>
great hiding spot
<willmore>
Too bad we can't sell them to anyone under 21/18. Then again, that might simply support in the community. ;)
<willmore>
Did you mean Bear?
<willmore>
All boards will fit in a bear. You just have to get the bear to hold still for a bit.