ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
clegoffic has quit [Read error: Connection reset by peer]
atorgue has joined #armlinux
CLG has quit [Changing host]
CLG has joined #armlinux
atorgue__ has quit [Read error: Connection reset by peer]
adelaunay has joined #armlinux
<Xogium>
that is why you should setup certfp, folks ;)
adelaunay has quit [Quit: Leaving]
<CLG>
Will look into it thx
CLG is now known as clegoffic
<Xogium>
or even just plain sasl since libera supports it unlike oftc
<Xogium>
they got pretty good doc on it as well on the website
rvalue has quit [Ping timeout: 245 seconds]
<headless>
Xogium: is oftc working for you?
* headless
can't connect to it for some time...
Poltawer has joined #armlinux
rgallaispou has joined #armlinux
<Xogium>
headless: yes, works good over here, I'm in atm at least
sszy has joined #armlinux
clegoffic has left #armlinux [Leaving]
apritzel has joined #armlinux
rvalue has joined #armlinux
clegoffic has joined #armlinux
headless has quit [Quit: Konversation terminated!]
xvmt has quit [Ping timeout: 244 seconds]
<wens>
broonie: would it make sense to use the regulator coupler stuff to model "one regulator that needs to follow another regulator within a certain voltage spread range"?
<wens>
for example, regulator A's voltage always needs to be 0.1V ~ 0.2V above regulator B's voltage
xvmt has joined #armlinux
bangcat has joined #armlinux
<krzk>
kbingham_: Last commits to your kmake are 10 YO (https://github.com/kbingham/kmake) so I wonder: do you still use it? Do you still develop it? Do you know any newer forks?
<krzk>
Except Abel's fork :)
<kbingham_>
ohh what did I do there?
<kbingham_>
What's abels fork ?
<kbingham_>
That looks like something I was pulling from an idea based on my usual kernel build system. I was probably trying to abstract it out.
<krzk>
I mean, github reports Abel's fork as the only one, so I wanted to avoid obvious answer to my question about forks :)
<kbingham_>
It's funny - I have no recollection about making that repo at all but that's what happens after 10 years :D
<krzk>
So I guess you do not use it anymore?
<kbingham_>
The system I use most is 'kbuilder' which is proabbly what that kmake was going to be a cleaned up version of.
<kbingham_>
let me make sure I push the latest of that.
<kbingham_>
the concept is a directory per board - and I can cd into that directory and run "make" and it does everything I need to build a kernel and run the board ;-)
<kbingham_>
It hooks into my board farm automation - so my workflows are usually "make debix" ... (in the debix folder) - and it will build the kernel/dtb, copy the Image/dtb/fit whatever to the tftp server - and then power the board down and back on again - and then the board is running the new kernel ;-)
<krzk>
kbingham_: some short readme would be useful how to use. Does it have to be as subdir of kernel repo?
<kbingham_>
Presently - I don't think I expected other people to use it.
<kbingham_>
the kbuilder clones a kernel into sources/linux/
<kbingham_>
while I think (digging in my memory) kmake was proabbly trying to do similar things for an existing kernel source? Ultimately - my use cases are to keep the kernel configurations under version control along with the infra that lets me build that config and run it.
<kbingham_>
Are you looking to update your workflow? I imaging you're quite used to building kernels etc...
<krzk>
yeah, you can achieve it with kmake as well - just symlink.
<krzk>
kbingham_: I use my own toolset which has 12 years which means it solves my problems I expereienced 12, 11, 10,9 ... 1 years ago ,and since I do not clean things that aggresively, it grew to a monstrosity, so I am thinking that maybe I should abandon it entirely and switch to something new
<kbingham_>
aha :-) so you could switch your issues to my issues :D
<kbingham_>
But maybe we can combine issues and reduce them ... :D
<krzk>
It's one build script for everything - different archs, boards, targets (like coccicheck), config custoomizations etc. so you can imagine
<kbingham_>
Essentially - I separate myself from the rootfilesystems (buildroot/yocto/debian...) and the scripts I have focus on 'just build a kernel modules and dtb and make these run on a target.
<kbingham_>
Which I expect is the only thing that matters to most kernel developers ;-) - and of course - anything that requries writing an SD card and moving from my chair to replace a card is out - so it has to be automated :D
fvincenzo has joined #armlinux
<kbingham_>
Laurent has his own similar kbuild.sh system too - but of course I didn't write that so I don't use it ;D
<kbingham_>
it looks like I had some good initial ideas with that kmake repo - I expect I hit -ENOTIME or just didn't continue it, as I was working in my own kbuilder environments etc.
<j`ey>
there's also tuxmake
<kbingham_>
I can't see reference to abels fork - what's the link for taht ? I'm curious to know what someone did on top :D
<krzk>
Obviously as Liinaro made tuxmake I know it :), but this is completely different
<krzk>
although maybe it also has features of building locally - without tuxsiote
<kbingham_>
interesting - I have ~/bin/kmake which looks newer than what's in that repo too... But I bet anything I did would have been on my much older laptop :S
<abelvesa_>
kbingham_: not much, except that notify command override thingy, which is already pushed to my fork
<kbingham_>
abelvesa_, Where's the fork ? I'm curios :D
<abelvesa_>
kbingham_: but I've been using it for a few months now and I'm really happy with it. So I guess I need to buy you a coffee :)
<kbingham_>
but I'm not sure if there's much of use in there ...
<kbingham_>
although I did seem to add automatic detection of notify-send ...
<abelvesa_>
kbingham_: nice, I'll pull that as well
<abelvesa_>
kbingham_: I do have a few things local, like export for LLVM and some DTB checks vars
<abelvesa_>
kbingham_: but those do not make sense to be added for now
<abelvesa_>
kbingham_: but do like a lot how versatile a kmake file can get with very specific targets ...
<kbingham_>
my intention for building kernels is to make sure we don't have to remember things like all the env vars, and I always want to keep the .config under version control - I'm not sure how I planned that with the kmake side - but https://github.com/kbingham/kbuilder/blob/master/build-common/packages/linux might have insights into some of the tricks I do most of the time.
grahamn has joined #armlinux
<abelvesa_>
kbingham_: right, but this kmake thing is simple enough for rapid kernel development
<kbingham_>
indeed.
<broonie>
wens: Yes, that's roughly what it's there for.
<broonie>
j`ey: tuxmake only does the build bit, it's not really helping with getting stuff onto the target (I use tuxmake, dump the results into s3 and then LAVA for the boards).
luispm has quit [Ping timeout: 252 seconds]
<abelvesa_>
kbingham_: one thing that I'd like this kmake to have is bash completion for targets found in the local kmake :D
<abelvesa_>
kbingham_: but listing them would also be good enough
rgallaispou has left #armlinux [#armlinux]
<kbingham_>
doesn't it find them with the existing bash completion ?
<kbingham_>
the bash completion is just directly from 'make' auto complete - so if you can autocomplete from an included file from within Makefile - it should be possible with the kmake includes too ?
<kbingham_>
(the easy/builtin autocomplete is one of the reason I like the Makefile 'base' too )
<abelvesa_>
kbingham_: wait, it does find them. Nice!
<kbingham_>
:-#
<kbingham_>
:-)
Poltawer has quit [Ping timeout: 248 seconds]
Poltawer has joined #armlinux
luispm has joined #armlinux
jfsimon has quit [Remote host closed the connection]
jfsimon has joined #armlinux
jfsimon has quit [Remote host closed the connection]
jfsimon has joined #armlinux
rgallaispou has joined #armlinux
rvalue has quit [Ping timeout: 276 seconds]
rvalue has joined #armlinux
Poltawer has quit [Quit: WeeChat 4.6.3]
atorgue1 has joined #armlinux
atorgue has quit [Read error: Connection reset by peer]
rgallaispou has quit [Read error: Connection reset by peer]
headless has joined #armlinux
prabhakalad has quit [Read error: Connection reset by peer]
clegoffic has quit [Quit: Client closed]
clegoffic has joined #armlinux
masneyb has joined #armlinux
jfsimon has quit [Remote host closed the connection]
jfsimon has joined #armlinux
prabhakalad has joined #armlinux
Peng_Fan has quit [Quit: Connection closed for inactivity]
HerbY_NL has joined #armlinux
sally_ has quit [Changing host]
sally_ has joined #armlinux
sally_ is now known as sally
HerbY_NL has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
gclement has quit [Quit: Leaving.]
jfsimon has quit [Remote host closed the connection]
jfsimon has joined #armlinux
HerbY_NL has joined #armlinux
HerbY_NL has quit [Quit: My Mac has gone to sleep. ZZZzzz…]