ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | Armbian 20.11 Tamandua released | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Type 'help' for help | Logs: -> irc.armbian.com
Glock24 has quit [Ping timeout: 240 seconds]
Glock24 has joined #armbian
s_frit has quit [Remote host closed the connection]
nekomancer[m] has quit [Ping timeout: 244 seconds]
t4h4[m] has quit [Ping timeout: 244 seconds]
TiD91 has quit [Ping timeout: 240 seconds]
psydruid has quit [Ping timeout: 240 seconds]
Sebastian[m]1 has quit [Ping timeout: 243 seconds]
kprasadvnsi[m] has quit [Ping timeout: 246 seconds]
MaxT[m] has quit [Ping timeout: 265 seconds]
tionebrr has quit [Ping timeout: 265 seconds]
loredin has joined #armbian
solderfumes[m] has quit [Ping timeout: 260 seconds]
mrjpaxton[m] has quit [Ping timeout: 240 seconds]
t4h4[m] has joined #armbian
forest[m] has joined #armbian
psydruid has joined #armbian
Sebastian[m]1 has joined #armbian
kprasadvnsi[m] has joined #armbian
tionebrr has joined #armbian
nekomancer[m] has joined #armbian
t4h4[m] has quit [Ping timeout: 241 seconds]
psydruid has quit [Ping timeout: 241 seconds]
Sebastian[m]1 has quit [Ping timeout: 258 seconds]
nekomancer[m] has quit [Ping timeout: 258 seconds]
tionebrr has quit [Ping timeout: 265 seconds]
kprasadvnsi[m] has quit [Ping timeout: 265 seconds]
forest[m] has quit [Ping timeout: 244 seconds]
kprasadvnsi[m] has joined #armbian
emanuele-f has quit [Ping timeout: 256 seconds]
emanuele-f has joined #armbian
s_frit has quit [Remote host closed the connection]
s_frit has joined #armbian
emanuele-f has quit [Ping timeout: 265 seconds]
emanuele-f has joined #armbian
nekomancer[m] has joined #armbian
tionebrr has joined #armbian
psydruid has joined #armbian
TiD91 has joined #armbian
solderfumes[m] has joined #armbian
t4h4[m] has joined #armbian
forest[m] has joined #armbian
MaxT[m] has joined #armbian
Sebastian[m]1 has joined #armbian
mrjpaxton[m] has joined #armbian
pinkieval has quit [Ping timeout: 264 seconds]
pinkieval has joined #armbian
pinkieval has quit [Excess Flood]
pinkieval has joined #armbian
pinkieval has quit [Excess Flood]
pinkieval has joined #armbian
archetech has joined #armbian
cisco87 has quit [Remote host closed the connection]
cisco87 has joined #armbian
BCMM has joined #armbian
Naka has quit [Remote host closed the connection]
Naka has joined #armbian
cisco87 has quit [Ping timeout: 268 seconds]
cisco87 has joined #armbian
Nakaori has joined #armbian
Naka has quit [Ping timeout: 256 seconds]
peterm6881 has joined #armbian
peterm6881 has quit [Quit: Leaving]
archetech has quit [Ping timeout: 256 seconds]
archetech has joined #armbian
Glock24 has quit [Ping timeout: 256 seconds]
Glock24 has joined #armbian
grillon has joined #armbian
<grillon>
Hi there
<Werner>
Hi
<grillon>
tell me if I'm wrong, packages bianry are compatible between different board. What is specific is the kernel, kernel config, boot config and firmwares right?
<Xogium>
not always
<grillon>
in case it's arm based?
<Xogium>
if you try to install a package meant for a 64 bit arm device on a 32 bit arm, well. Needless to say it won't go as planned
<grillon>
ok but arm32 on arm64?
<grillon>
and all arm32 on arm32 it's compatible right?
<Xogium>
you still need the arm 32 libs to run it. If you don't have those then the program will simply not run. Also, some SoC are backward compatible, and some aren't
<Xogium>
your kernel also needs to support running 32 bit code
peterm6881 has joined #armbian
peter_ has joined #armbian
<Xogium>
as for arm 32 on arm 32, it depends, but you might be able to run a armv6 binary on armv7
<Xogium>
but not armv7 on armv6, possibly
<Xogium>
and then there's armv5 but that's quite old by this point
peterm6881 has quit [Client Quit]
peter_ has quit [Client Quit]
peterm6881 has joined #armbian
<Xogium>
there's also 32 bit armv8
<grillon>
ohh ok armv8 is not 64bit?
<Xogium>
it can be either 32 or 64
<Xogium>
usually 64, but 32 is doable
<grillon>
ok I see thank you for all these precious informations :-)
<Xogium>
grillon: np :)
<Xogium>
grillon: more generally, if you get some programs to work on another machine, its also a nice dose of luck. There's no 100% guarenty that whatever you have built as binary will work on another target, especially if that target doesn't use the same libc, or same version of any given libs it might call
grillon has quit [Quit: Ping timeout (120 seconds)]
grillon has joined #armbian
grillon has quit [Changing host]
grillon has joined #armbian
<grillon>
sorry I have been disconnected by webchat :-(
<grillon>
I could have trouble with some library in case I want to use binary from an OS to another but in case it's the same OS it should be the same libc right?
<Xogium>
logically yeah, if they run the exact same version, are up to date, and such
<Xogium>
should all work okay
<grillon>
ok good thank you. I'm interested in a project which run on another platform than mine and I was wondering how to port this project. I was quickly comparing install in on another os and copy the package stack or adpate the os to my system...
<Xogium>
well you could try. Just nothing that would guarenty it working
<grillon>
yes you are right both solutions have pro and cons
<Tonymac32>
IgorPec that beer is very dark, so if that's what you like, it should be ok. I only get one every now and then XD I think Chwe tried it once, the name is the reason buy it the first time :D
<grae>
and I've dug into the innards of that Tegra chip. The kernel's split across multiple repositories, there's multiple incompatible 4.9 branches, and honestly NVidia's support on the forums is a little like pissing in the wind
<stipa>
in short
<stipa>
guys who develop Armbian images work solo
<stipa>
like
<stipa>
one guy one board
<IgorPec>
that's lowest, yeah, but we have some boards/families with more folks
<stipa>
so, your board with wierd UART is your thing, but you would get support
<grae>
I get that. I'm sure I could probably get some help digging in if I was doing it, but it's a big ask of someone else
<IgorPec>
sadly, nvidia jetson seems like a propriatery linux only
<IgorPec>
that's not very close to community efforts
<grae>
yes and no. they have public repositories, but they're not easy to find
<grae>
and you're right, it's not
<IgorPec>
private means more like kernel is heavily modified and can't be minstreamed
<grae>
I suspect you're right on that, not without some massive effort
<IgorPec>
it has full of non-standard solutions, closed parts,
<IgorPec>
yes. and there is little to none activity to get things upstramed
<IgorPec>
to me, it looks like nvidia has no interest
<grae>
and I'd agree with that
<stipa>
nividia and linux is not realiable
<stipa>
they look on everything through profit
<stipa>
so hackery and exploration is not their thing
<stipa>
it's not nvidias interest
<grae>
nope, it's machine vision, and self driving cars
<stipa>
right, that's huge thing now and even bigger in the future
<IgorPec>
they just don't care and don't need to do anything about
<grae>
The computer engineer in me finds it interesting as I think that Tegra was NVidia learning to build their own CPUs ...
<IgorPec>
could be. but in last decade, everyone is making their own cpu :) apple, amazon
<grae>
Tegra has always had a "companion core", which always existed for no clear reason, but were the "high power" cores in the TX2 and the only ones installed in the successor
<grae>
but then NVidia bought ARM, so I have no idea what their plan was ...
<IgorPec>
business background is difficult to judge from this postion
<IgorPec>
from technical position i mean
<grae>
absolutely, I have no doubt they were playing multiple positions
<IgorPec>
arm is very important player in making cpu
<IgorPec>
and making cpus is very important too
<stipa>
arm is like stripped down intel or amd
<grae>
yes, but I think RISC-V is going to eat ARM alive in about 10 years
<IgorPec>
why?
<Tonymac32>
unless a company like ARM supports it, it won't
<stipa>
open hardware
<grae>
because the recent spat between the US govt and China
<grae>
US govt clamped down on licensing, so they're going to develop architectures that don't require licenses
<IgorPec>
open hardware is like democracy and freedom. nice to have, but ..
<grae>
same reason Huawei immediately announced Harmony OS
<Tonymac32>
right, with the investment of massive corporations. We'll see if anyone seriously invests in RISC-V
<IgorPec>
it works, it would be nice, but underestimating patent establishment and big business ain't good
<grae>
they're going to start slow, but if the Apple M1 is any indication, massive investment might make waves
<Tonymac32>
I follow RISC-V closely, I don't think it will be more than a curiosity and a hype engine for at least 5 years, then it will begin to make progress
<IgorPec>
they will sertainly support if it will bring money
<IgorPec>
but most of the people doesn't care about openenes
<IgorPec>
we do
<IgorPec>
engeneers, community, freedom fighters
<stipa>
grae: but, there's guy here TRS-80 who said that RISC V is not so open source as we think
<stipa>
soooooooooooooooooo
<IgorPec>
stipa: that's also quite possible
<Tonymac32>
stipa it's an architecture. The cores made with the architecxture don't have to be open at all
<grae>
right, so the ISA and the architecture is license free. But a commercial core doesn't have to be
<grae>
and if folks are free to implement closed hardware around it, we're back to the proprietary issues igor mentioned earlier
<stipa>
guess what
<stipa>
what hardware will actually be built
<stipa>
and available on the market
<stipa>
propbably not hose that are open source
<stipa>
but some rpi kind of crap chips
<Tonymac32>
so the stripped down microcontroller from RPI surprised me in not being RISC-V actually
<stipa>
that'll be " OPEN SOURCE MY ASS"
<grae>
for the first few years, yes
<IgorPec>
closing things is securing your investment. from business perspective
<IgorPec>
but community can build things under some open licence
<IgorPec>
and share.
<Tonymac32>
The open FPGA guys are doing cool stuff with RISC-V
<Tonymac32>
otherwise I see very little impact other than seeing China move from 8051 to RISC-V
<stipa>
i don't know, competing with all those giants with open source chips that everyone will want to buy is just not giants really want
<stipa>
not what*
<stipa>
they'll go out of busniess
<stipa>
so
<stipa>
you as a small chip manufacturer coming to the market
<stipa>
with open source hardware
<stipa>
is likely to work
<Tonymac32>
so I can't afford to toss something at TSMC for fab, I don't know about you
<stipa>
i can barely afford a rpi
<stipa>
i don't have one so
<stipa>
i'm poor enough
<stipa>
not to start the revolution
<stipa>
because those fabs won't develop chip for free
<stipa>
we, the poor people just have to deal with what's thrown at us
<grae>
I must go. later all
<IgorPec>
l8r
<stipa>
cya
grae has quit [Quit: Leaving]
<Tonymac32>
later
<Tonymac32>
igorpec I did you see my note about apt-update on the zfs-dkms?
<Tonymac32>
It worked, but I had to do the install twice. Maybe doing it at the same time as the kernel was the issue
<IgorPec>
didn't notice, where?
<Tonymac32>
here yesterday or day before
<IgorPec>
i made many tests and didn't ran into any issue yet
<Tonymac32>
anyhow, I did an apt-update from kernel 5.8 to 5.9 and zfs 0.85 to 2.01
<Tonymac32>
the make failed on the zfs package, had to dpkg-setup or whatever afterward
<Tonymac32>
on the second pass it had no problem
<IgorPec>
huh
<Tonymac32>
helios64*
<IgorPec>
debian?
<Tonymac32>
Focal
<IgorPec>
i will try to recreate, but i haven't seen anyone else complaining on forum
<IgorPec>
but first i have to order the beer you have recommended :)
<Tonymac32>
haha
<Tonymac32>
it's a different one, so I can't promise anything XD
<IgorPec>
i am not particular fan of beers with overtaste, but to try out
<IgorPec>
this beershop is largest in the area and in my walking distance :)
<stipa>
"Jantarno rdeče pivo, aromatično prežeto z bourbonom, vanilijo, karamelo in sladom. Svileno gladek okus sladu in karamele ter sladen prehod v dolg, suh pookus."