LocutusOfBorg has quit [Quit: ZNC 1.8.2+deb3 - https://znc.in]
LocutusOfBorg has joined #yocto
xmn has joined #yocto
frieder_ has quit [Ping timeout: 245 seconds]
jpanisbl has quit [Quit: Konversation terminated!]
tgamblin has joined #yocto
frieder_ has joined #yocto
manuel1985 has joined #yocto
frieder_ has quit [Ping timeout: 272 seconds]
LocutusOfBorg has quit [Ping timeout: 245 seconds]
LocutusOfBorg has joined #yocto
amitk_ has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
kscherer has joined #yocto
amitk_ has quit [Ping timeout: 260 seconds]
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
frieder_ has joined #yocto
amitk_ has joined #yocto
amitk has quit [Ping timeout: 246 seconds]
Yash88 has quit [Quit: Client closed]
frieder_ has quit [Ping timeout: 272 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Guest98 has quit [Quit: Client closed]
dacav has joined #yocto
Guest98 has joined #yocto
<Guest98>
i did a small project in Yocto and many people helped me here while doing this project. i want to write the names of these helpful people on the github. that shouldn't be a problem, right? i wanted to ask.
<rburton>
the logs here are public so it's not exactly a secret
<rburton>
personally, public thanks are always welcome
rob_w has quit [Quit: Leaving]
<Guest98>
rburton but i dont know under which title i should thanks. contributors maybe?
<rburton>
a Thanks section seems sensible
<Guest98>
rburton thank you!
Guest98 has quit [Quit: Client closed]
olani has joined #yocto
sakoman has joined #yocto
frieder_ has joined #yocto
florian__ has joined #yocto
Maxxed has joined #yocto
prabhakar has joined #yocto
prabhakarlad has joined #yocto
zelgomer_ is now known as zelgomer
frieder_ has quit [Ping timeout: 272 seconds]
<smooge>
that was nice of them
<JPEW>
RP: ptest-runner may not be very recongizable anymore, for better or worse. I do think that the new approach might fix some of the intermittent ptest bugs though
<JPEW>
I'm _pretty_ sure there was a race where the output from a ptest might get lost or categorized under the wrong test suite... have we need the number of tests for a suite vary from run to run?
<JPEW>
s/need/seen/
goliath has quit [Quit: SIGSEGV]
<RP>
JPEW: we've seen a few odd behaviours
<JPEW>
I really thought ptests ran in parallel.... sorry for the churn
<RP>
JPEW: I'm trying to get to the point our regressions analysis is better but its proving tough
<ecdhe>
Not a yocto question but I'm doing a board bringup. I have linux booting but some of my peripherals aren't talking. I'm dumping their registers with devmem, but I'd like to dissect the values I read back, there are about 80 that are relevant and I'm having to look each one up in the datasheet.
<RP>
JPEW: we have enough problems running them serially :/
<ecdhe>
Ideally, I'd have a nice dissector like wireshark, but for the memory space instead of for a packet header.
<ecdhe>
Is there a tool meant for this kind of thing?
<JPEW>
On a related note, I have patches to run ptest tests in parallel, but it requires buffering the test output temporarily so it can be written out serially to the log for OE-selftest to parse
<JPEW>
Ya, fair
<RP>
JPEW: I'm just going to trust you on these patches
<JPEW>
RP: I tested them with oe-selftest, so I think it's good to go. It does fix the problems that were reported here
<RP>
JPEW: I will run it through master-next along with some other changes
<JPEW>
RP: Cool, thanks
prabhakarlad has quit [Quit: Client closed]
frieder_ has joined #yocto
frieder_ has quit [Remote host closed the connection]
<khem>
zeddii: yeah I think it has to be sorted by kernel community and openzfs community first, for now may be folks wanting to use zfs can stick to 6.1 on aarch64
<ecdhe>
I found some options. I had been searching for "dissection" of binary files and register maps. The term that finally found me tools was "binary parsing"
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
mckoan is now known as mckoan|away
manuel1985 has quit [Quit: Leaving]
alessioigor has quit [Quit: alessioigor]
Kubu_work has quit [Quit: Leaving.]
gsalazar has quit [Ping timeout: 264 seconds]
goliath has joined #yocto
Minvera has joined #yocto
nerdboy has quit [Ping timeout: 272 seconds]
rfuentess has quit [Remote host closed the connection]
__ad has joined #yocto
__ad has quit [Changing host]
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
florian__ has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
leon-anavi has quit [Quit: Leaving]
Kubu_work has joined #yocto
cavejohnson has joined #yocto
<vvn>
does bitbake -f -c cleanall -c compile foo works or the two tasks must be specified on two command lines?
Haxxa has quit [Quit: Haxxa flies away.]
cavejohnson has quit [Ping timeout: 272 seconds]
Haxxa has joined #yocto
brrrm has joined #yocto
brrm has quit [Ping timeout: 245 seconds]
mvlad has quit [Remote host closed the connection]
goliath has quit [Quit: SIGSEGV]
schtobia has quit [Quit: Bye!]
schtobia has joined #yocto
vladest has quit [Ping timeout: 252 seconds]
<RP>
vvn: I'd not do that as it will race
* RP
had never considered that set of problems before :/
amsobr has quit [Quit: Konversation terminated!]
* zeddii
has menuconfig fixed.
Kubu_work has quit [Quit: Leaving.]
hrberg has quit [Ping timeout: 245 seconds]
GNUmoon has quit [Ping timeout: 240 seconds]
GNUmoon has joined #yocto
hrberg has joined #yocto
sgw has quit [Remote host closed the connection]
sgw has joined #yocto
alessioigor has joined #yocto
<RP>
zeddii: I dread to think how it broke this time :/