<jclsn>
What is the best way to set the RTC system wide? Just set in the kernel via RTC_HCTOSYS_DEVICE?
BWhitten has quit [Ping timeout: 248 seconds]
BWhitten has joined #yocto
rich1234 has quit [Quit: Client closed]
amitk_ has quit [Ping timeout: 260 seconds]
sakoman has joined #yocto
xmn has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<qschulz>
jclsn: look into what hwclock does and do it :)
PobodysNerfect has quit [Remote host closed the connection]
PobodysNerfect has joined #yocto
<mason>
paulg: Did you play with Jarts when you were little? I had them.
<paulg>
oh yeah, I remember playing with them on my grandparents lawn.
<paulg>
I don't recall any of us getting impaled though.
<paulg>
of course, kids being kids, we quickly got bored of aiming for the plastic hoop and then predictably started to see who could throw them the highest...
<fray>
I can remember them ONCE when I was young, then they got recalled and 'went away'
<fray>
lol
<fray>
(I wasn't old enough to play with them, but I was fascinated with my parents playing with them)
<fray>
must have been 1980 maybe?
leon-anavi has quit [Read error: Connection reset by peer]
leon-anavi has joined #yocto
<fray>
wow they weren't outlawed until 1988?! There is no damned way we had them past 1984.. I figured my parents went "nope" on them closer to 1980
rich1234 has joined #yocto
<paulg>
and yeah, I'm sure the turds were responsible for a lot of roof/shingle damage too.
<linex[m]>
hello, is there a way to manually use kernel-yocto-tools like kgit-s2q and kgit-scc ? I can't find these scripts/files and the bitbake shell is not helping.
<linex[m]>
Thank you!
leon-anavi has quit [Remote host closed the connection]
perceval[m] has quit [Quit: You have been kicked for being idle]
jclsn has quit [Ping timeout: 252 seconds]
jclsn has joined #yocto
mckoan is now known as mckoan|away
otavio has quit [Remote host closed the connection]
otavio has joined #yocto
seninha has quit [Quit: Leaving]
frieder has quit [Remote host closed the connection]
pidge has quit [Read error: Connection reset by peer]
Estrella has joined #yocto
zpfvo has quit [Remote host closed the connection]
pidge has joined #yocto
rfuentess has quit [Remote host closed the connection]
<rburton>
yeah anonymous intel hardware, who knows what it is
florian has joined #yocto
<paulg>
I had the misfortune to go looking into i915 code recently
<paulg>
some preempt-rt issue.
<paulg>
what struck me, and I guess I should have known...
<paulg>
is that i915 essentially contains support for every turd since a 2003 Pentium4 platform.
<paulg>
there is no Kconfigs to narrow down what is or isn't supported.
rich123 has joined #yocto
alessioigor has quit [Quit: alessioigor]
<paulg>
so if someone reports a bug on "i915" you pretty much need to know exactly what the hardware was or you'll probably never reproduce the issue since you won't run that code.
alessioigor has joined #yocto
rich123 has quit [Ping timeout: 255 seconds]
nerdboy has quit [Ping timeout: 250 seconds]
kscherer has quit [Quit: Konversation terminated!]
kevinrowland has joined #yocto
kscherer has joined #yocto
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
<kergoth>
ouch
florian has quit [Ping timeout: 255 seconds]
<khem>
backward compatibility is good with intel platforms I see that as strength but yes there will be complexity somewhere
<paulg>
now if only bugzilla included the link in plain text that you could see in mutt after w3m de-htmlizes it...
<paulg>
I guess only old dinosaurs use text e-mail clients.
* paulg
makes a feeble attempt to remember rburton 's tip for more than a day
maoti__ is now known as jpuhlman
<vvmeson>
rburton: Thanks. I have a firefox seaerch engine shortcut so open a new tab, type ypbz <anything> and that matches the number or does a search. Small but useful feature that I also use for looking up recipes quickly.
* vvmeson
will be espousing the joys of a Neural Link shortcut before you know it!
<LetoThe2nd>
Nostromo35: I don't think devtool is a magic way to add a binary package from another distro. its more like a kickstart thing to add a source based thing.
<LetoThe2nd>
fray: hey, do you happen to know the state of zedboard? last traces i see are in meta-xilinx on zeus
<fray>
Do you know which zedboard?
<LetoThe2nd>
fray: "Xilinx zynq 7000 SoC developement Board - Zedboard" is what i got in a PR
<fray>
there is a zedboard there.. but be careful, we split things up, meta-xilinx-vendor means it's using a Xilinx SoC, but it's NOT a xilinx board
<fray>
I don't have access to a zedboard to even try it, so it's entirely possible it's no longer available -- and if it is available may or may not work
<Nostromo35>
Yes, but I thought the -b argument would allow for binary packages. Currently, it's failing due to a lack of a control.tar.gz file.
<paulg>
clearly zeddii must have a zedboard
<fray>
(link I posted is to the recent Mickledore update we did.. I havn't update git.yoctoproject.org version yet, was going to do that today)
* paulg
runs
<LetoThe2nd>
fray: ah nice, thanks. neither have i, but a community member said they did "mender support for zedboard", and lets say, the state leaves quite a bit to be improved.
<fray>
the new structure of meta-xilinx (repository) is meta-xilinx-bsp are _our_ reference boards, meta-xilinx-vendor are third party reference boards, which should work (but havn't been tested by us.. if someone reports them as broken then they will get moved....) meta-xilinx-contrib is for things that may be broken that we have no way to enable/support..
<fray>
so if a -vendor item is broken it and the vendor is unresponsible, then it may move to contrib.. if they continue to be unresponsive it will eventually go away
<LetoThe2nd>
Nostromo35: stupid question, what would be a reason to pull in libc instead of using, well, the libc yocto builds?
<fray>
(the only vendor board I regularly have access to is the 'ultra96')
<paulg>
fray, that sounds more like a gasoline than a board.
<fray>
(git.yoctoproject.org is the YP branches only of the github version, and usually lags a couple of days in case we push something out that is horribly broken)
<LetoThe2nd>
fray: no problem, to be brutally honest I just couldn't find anything in the layerindex after zeus. so there seems to either be some non-indexed layer involved, or breakage.
<fray>
Layer index was broken last time I looked for some layers...
<LetoThe2nd>
quite possible, indeed.
<fray>
Since we just updated some of this, I'm not sure we updarted the layerindex to the new paths.. I'll need to go check
<fray>
basically I give the meta-xilinx-vendor stuff (other then ultra96) a 50/50 chance of working.. ultra96 worked 2 weeks ago
<fray>
I give the -contrib stuff only a 10% chance of actually working, but it builds.. :P
<LetoThe2nd>
fray: thats good enough for me, I'll give it a spin. i just want to give the submitter something better to work on than just "what you sent me is warrior, nah"
<fray>
ya.. 3 weeks ago, the meta-xilinx-bsp was in ROUGH ROUGH shape.. but everything there should now work
<fray>
too us forever to get things recovered after a few years of effectively code rot
<Nostromo35>
Thanks Leto, I think that's led me onto the right track.
<LetoThe2nd>
fray: nitpick gh meta-xilinx seems to have a kirkstone-next branch, but no kirkstone...
zhmylove has quit [Quit: Leaving]
<fray>
correct, there is no supported kirkstone
<fray>
we do have a supported Langdale and now Mickledore
<LetoThe2nd>
hm ok
<fray>
Langdale branch is supported as it's the basis of our upcoming 2023.1 release.. Mickledore is temporary, but will be supported through the Mickledore cycle (I hope).. going to start on master and such once it diverges enough
<LetoThe2nd>
i see. like i said, just trying to find a starting point for folkses who are basing frankenstuff on warrior
<fray>
My official position is "you should talk to an ISV/OSV if you are creating product, otherwise look at whatever the latest PetaLinux version is." (for someone YP knowledgable, but doesn't want an OSV, then we're still "working on it"
<LetoThe2nd>
right PetaLinux might be another place to set them up
* vvmeson
wonders if RP will have a theme of naming releases after monsters: beowulf, frankenstein, godzilla, trump, dracula, krueger, kingkong, ...
BWhitten has joined #yocto
<LetoThe2nd>
vvmeson: my vote always is on diseases
<LetoThe2nd>
just now as we talk about it, "coma" sounds like a perfect release name for an LTS.
<LetoThe2nd>
fray: i take it this CONFIG_DTFILE or SYSTEM_DTFILE is something the machine has to set?
<fray>
depends on the confgiuration. If you use meta-xilinx-tools.. don't need to set it, everything is generated.. if you don't use that then you need to have a functional device tree.. 'system_dtfile' is the system wide DTB, config_dtfile is a specific 'domain' config file, a system DTB can cover more then just a linux domain, i.e. including the cortex-r5, microblaze parts, etc..
<fray>
the current System Device Tree stuff isn't out yet, should be soon.. and when it is.. it SHOULD make more sense
<LetoThe2nd>
fray: k. stupid question, should a board in meta-xilinx-bsp build out of the box?
<fray>
meta-xilinx-bsp "yes", but by default it requires meta-xilinx-tools..
<LetoThe2nd>
ah ok
<fray>
you need meta-xilinx-core, meta-xilinx-bsp and meta-xilinx-tools layers
<fray>
if you pre-generate the device tree and firmware artifacts, then you can skip meta-xilinx-tools... but that isn't really documented yet
<fray>
(meta-xilinx-tools is an interface to a cut down version of Vivado, our hardware tooling, that can process a hardware description file (XSA) and generate the device tree, build the firmwares, etc)
<fray>
We've got chips that enable 'microblaze', which AFAIK is a FPGA loaded "soft" CPU. Zynq7 which is an ARM9 (single domain).. ZynqMP (or UltraScale+) which is cortex-a53, but also has an embedded [hardware] microblaze on it and cortex-r5.. and the newer versal line which is a cortex-a72, two microblaze [for the firmware], and cortex-r5 as well..
<fray>
it SHOULD be in the readme file in the main directory or meta-xilinx-core..
<fray>
meta-xilinx-bsp itself doesn't ACTUALLY require meta-xilinx-tools -- but without it, there is a lot of manual configuration needed..
<LetoThe2nd>
fray: there is that you need to provide the file, but meta-xilinx-tools doesn't seem to be mentioned. or i'm too tired by now to see it, its 10:30pm
ramok has joined #yocto
* LetoThe2nd
will call it a day then. have fun folks!
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 250 seconds]
mvlad has quit [Remote host closed the connection]
nemik has joined #yocto
Finn[m] has joined #yocto
kevinrowland has quit [Quit: Client closed]
Nostromo35 has quit [Ping timeout: 260 seconds]
florian has quit [Ping timeout: 276 seconds]
alessioigor has quit [Quit: alessioigor]
seninha has joined #yocto
Minvera has quit [Remote host closed the connection]
kscherer has quit [Quit: Konversation terminated!]
kscherer has joined #yocto
kscherer has quit [Client Quit]
mkazantsev has joined #yocto
invalidopcode1 has quit [Remote host closed the connection]