<Wizzup>
Pali: what do you think about extending include/configs/nokia_rx51.h for reading dtb/ftd files?
<Wizzup>
currently it only works with initrd
<Pali>
Do you mean to read DTB and use it for booting if exists?
<Wizzup>
yes, like bootz kernaddr - dtbaddr
<Wizzup>
currently it searches for any initrd if the env var is set, but it doesn't do that for dtb
<Pali>
why not? seems like a good idea
<Wizzup>
ok
<Pali>
would you provide a patch for it?
<Wizzup>
yeah, if there are no size concerns because it would increase the size of the script by a bit?
<Pali>
you have to check
<Wizzup>
I suppose they will also bug me for the musb dm conversion then ;)
<Pali>
you can open a pull request to u-boot on github... opening pull request is just for running CI tests, nothing more
<Pali>
and CI test checks also u-boot size for n900
<Pali>
so if it passes then there should not be any issue
<Wizzup>
ok
<Pali>
but IIRC kabel enabled LTO support for u-boot n900, so there should be more space
<Wizzup>
ok
Wikiwide has joined #maemo-leste
optix has quit [Ping timeout: 240 seconds]
devrtz[m] has quit [Ping timeout: 240 seconds]
devrtz[m] has joined #maemo-leste
optix has joined #maemo-leste
Pali has quit [Ping timeout: 245 seconds]
Daanct12 has joined #maemo-leste
Danct12 has quit [Ping timeout: 252 seconds]
Daanct12 has quit [Remote host closed the connection]
macros_ has quit [Ping timeout: 240 seconds]
macros_ has joined #maemo-leste
joerg has quit [Ping timeout: 252 seconds]
joerg has joined #maemo-leste
Danct12 has joined #maemo-leste
<freemangordon>
Wizzup: I decided to revert changes I made for libhildonmime
<freemangordon>
or at least will remove pre-depends I put there
<freemangordon>
tmlind: what is the correct way to use clear_page()?
<freemangordon>
hmm,scratch that, I guess it is userspce that shall clear the buffers
<freemangordon>
Wizzup: check your mail, I will take care of omap DDX
<freemangordon>
good, xrandr refuses to rotate to portrait
<freemangordon>
on n900 that is
inky_ has quit [Read error: Connection reset by peer]
<freemangordon>
Wizzup: ping
xmn has quit [Ping timeout: 256 seconds]
inky_ has joined #maemo-leste
<freemangordon>
Wizzup: omap ddx and leste-config are fixed to support both n900 and mapphone displays, so, the only missing thing is the kernel
<Wizzup>
ok
<Wizzup>
freemangordon: pong
<Wizzup>
freemangordon: so this new patch replaces the older patch?
inky_ has quit [Ping timeout: 256 seconds]
<Wizzup>
freemangordon: droid3-dev is running on image-builder-32bit
inky_ has joined #maemo-leste
<freemangordon>
Wizzup: yes
<freemangordon>
old one has a bug
<Wizzup>
good
<Wizzup>
I puled it in
<Wizzup>
I will make a omap-linux repo today
<Wizzup>
(maybe just rename droid4-linux)
<Wizzup>
still I will need to do the dtb stuff that I talked about yesterday but that should be ok
<freemangordon>
also, this patch is a 'proper' patch (with description, sign-off, etc)
Pali has joined #maemo-leste
<freemangordon>
ok
<Wizzup>
freemangordon: no readdir errors in the new build log
<Wizzup>
so that's good news
wunderw2 has joined #maemo-leste
<wunderw2>
Hello :)
<Wizzup>
hi
<wunderw2>
I am connected via XChat on N900 :)
wunderw has joined #maemo-leste
wunderw2 has quit [Client Quit]
<Wizzup>
wunderw: we likely fixed the latest image bug, we'll know in a few hours
<wunderw>
I'm waiting for my second N900, I will test on that :)
<wunderw>
On my first, I have Fanoush's Boot Menu, where I can't add Leste item
<wunderw>
I will use U-Boot on the second
<bencoh>
silly question, but why not install a proper up-to-date uboot on the first one as well?
<wunderw>
I need to have BackupMenu
<bencoh>
I might be wrong, but I think it works there as well
<wunderw>
It works best with Fanoush's Boot Menu
<Wizzup>
well, for leste in the future we will probably require upstream u-boot
<Wizzup>
for booting zImage
<Wizzup>
like in the next week or so :)
<bencoh>
oh
<bencoh>
Wizzup: is it tested with fremantle as well?
<Wizzup>
although I suppose I could make a special n900 postinst
<Wizzup>
bencoh: yeah
<Wizzup>
pretty sure pali's CI uses fremantle kernel
<Pali>
yes! CI in upstream u-boot uses fremantle kernel
<bencoh>
:)
<freemangordon>
Wizzup: what about other images?
<freemangordon>
I see the latest images is still built on 65bit builder
<freemangordon>
*64bit
<Wizzup>
freemangordon: first I want to see if droid3-dev is ok
<Wizzup>
freemangordon: I already switched the others over to the 32 bit builder
<Wizzup>
we just need to hit build
<Wizzup>
but let me verify that it is ok first
<Wizzup>
I fixed the ssh problem that made it fail, but the bionic image is building now so will test that one...
inky_ has quit [Ping timeout: 240 seconds]
inky_ has joined #maemo-leste
<freemangordon>
ok
<Wizzup>
I will also look at making the virtual machine i/o faster
<Wizzup>
(it takes a bit too long imho)
<freemangordon>
mhm
inky_ has quit [Ping timeout: 256 seconds]
<crab>
Wizzup: for the uboot change, does that mean a potential reflash / reinstall?
<crab>
im fairly sure im not using the fanoush boot menu but i have a fairly adhoc handrolled weird install on my n900.
<Wizzup>
crab: I'll look at doing some postinst for the n900 specifically where we append the dtb and make a uImage
<crab>
let me see if i can try and figure out what i have and where i got it from
<crab>
im pretty confident editing things and making them work, im most concerned with an install that requires the least work going forward.
inky_ has joined #maemo-leste
<crab>
and im more than happy to just do a proper reinstall if thats the best way to achieve that.
<crab>
ill admit that when i first installed leste it went on its own partition but i now think its so superior to all the other shit on here i should just ONLY use it.
<Wizzup>
I don't know yet, I'll let you know
<crab>
thanks.
<crab>
oh i guess i should reboot the little dude as i just upgraded hildon wifi
<Wizzup>
freemangordon: ok, new image has fixed theme
<Wizzup>
I'll see if we can make it work with a postinst
n900 has quit [Ping timeout: 260 seconds]
<Wizzup>
probably can, just need to check
<Wizzup>
uvos: btw on bionic it looks like the rgb led is somehow coupled to touchscreen leds, I have it blink when it is on and the touchscreen leds blink too
<Wizzup>
(fresh image)
DPA has quit [Quit: ZNC 1.8.2+deb2~bpo10+1 - https://znc.in]
<Wizzup>
the annoying thing with doing it in postinst is that our kernel pkg really only has one postinst
<Wizzup>
we have: CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y
<Wizzup>
so I would assume this would work
<Wizzup>
err
<Wizzup>
I guess there isn't even an option for not supporting getting dtb from bootloader in linux
<Wizzup>
must be always on
<Wizzup>
maybe having appended dtb on somehow causes kernel to read appended dtb garbage
<Wizzup>
parazyd: ping, what do you think about having extra packages in droid4-linux's control file (like linux-image-n900 that just depends on the main kernel package) that have their own additional postinst to create zimage with dtb appended or even uImage, would that work?
inky has quit [Quit: IRC for Sailfish 0.9]
inky has joined #maemo-leste
<Wizzup>
uvos: droid4 devel image boots fine now
<Wizzup>
uvos: the wifi module doesn't probe though
alex1216 has joined #maemo-leste
<Wizzup>
actually I think debian has an /etc/kernel postinst dir so we can just insert scripts there for n900-
<Wizzup>
parazyd: ^^
<Wizzup>
what do you think?
<bencoh>
it would probably make it simpler for fremantle user to try leste
<freemangordon>
Wizzup: hmm, 32MiB for kernel?
<bencoh>
the other option would be to push the latest uboot version to maemo/maemo-extras
<freemangordon>
isn't 0x84008000 - 0x82008000 too much?
<freemangordon>
oh, I guess no, zImage is compressed
<freemangordon>
so it must be uncompressed somewhere I guess
<freemangordon>
Wizzup: if you ask me, creating uImage with attached dtb while installing on-device is the best option
<freemangordon>
there is postinst.d and preinst.d
<freemangordon>
a simple script in postinst.d that cats zImage and dtb and calls mkimage should do the job
<freemangordon>
that script should be part of leste-config-n900 I guess
<Wizzup>
freemangordon: so the way to read those bootz args is
<Wizzup>
kernel_addr initrd_addr ftd_addr
<Wizzup>
freemangordon: since we have no initrd addr we specify -
<freemangordon>
ok
<freemangordon>
Wizzup: still, I think creating uImage in postinst should be way easier for everybody once done
<Wizzup>
freemangordon: right /etc/kernel/postinst.d
<freemangordon>
mhm
<Wizzup>
yeah I think that makes sense
<freemangordon>
do you know who executes the stuff there?
<Wizzup>
keep in mind we do not use debian kernel, we have our own
<freemangordon>
yeah
<Wizzup>
but we use builddep from mainline
<freemangordon>
that's why my question
<freemangordon>
good that our kernel is compatible
<Wizzup>
right
<bencoh>
don't you use make deb-pkg (or whatever it is call nowdays)?
<Wizzup>
so I will try to make a control file which has omap-linux-image as actual kernel and modules and then aliases that depend on, with optional postinst hooks
<freemangordon>
"hook scripts for boot loaders must be named using the prefix zz- "
<Wizzup>
bencoh: sure, with patches
<freemangordon>
Wizzup: wait, why is that
<Wizzup>
freemangordon: it is not a hook for bootloader
<freemangordon>
Wizzup: still, I don;t think this script belongs to the kernel package
<freemangordon>
neither we need special kernel package for n900
<freemangordon>
I think it should be like:
<freemangordon>
1.one kernel package to rule them all
<freemangordon>
2. leste-config-n900 with postinst script that cats zImage+dtb and calls mkimage
<freemangordon>
thats all
<freemangordon>
and yea, I think this is hook script for bootloader
<freemangordon>
unless I dont; understand what do they mean by "bootloader hook"
<bencoh>
updating bootloader config in a special way maybe
<freemangordon>
yeah, maybe
<freemangordon>
not importeant really
<freemangordon>
*important
uvos has joined #maemo-leste
<uvos>
<Wizzup> uvos: btw I still see hangs sometimes on droid3, do you see them as well?
<uvos>
yes lots
<uvos>
allways hangs mid drawing frames
<uvos>
<Wizzup> uvos: btw on bionic it looks like the rgb led is somehow coupled to touchscreen leds, I have it blink when it is on and the touchscreen leds blink too
<uvos>
known issue, the ts buttons are connected - somewhere idk where
<freemangordon>
uvos: what version is omap ddx?
<uvos>
they share a regulator with the pannel and rgb led
<Wizzup>
uvos: could be pvr clock rate?
<uvos>
and are set on by the vendor kernel
<Wizzup>
mhm
<uvos>
so any time the mainline kernel sets eitehr of those on
<uvos>
the ts buttons light up
<uvos>
Wizzup: well the pvr clock rate is the same as on the 3.0 vendor kernel
<uvos>
its possible that moto used a different rate on the 2.6 kernel for solana
<uvos>
we can check that
<uvos>
but idk why
<uvos>
all the omap4 variants besides *70 have the same rating for sgx
<Wizzup>
ok
<Wizzup>
just not sure what else could cause it
<uvos>
well d4 also hangs
<uvos>
if you load sgx esspecaly
<parazyd>
Wizzup: I have to think about that a bit re: postinst
<uvos>
so maybe d3 just shows it sooner for some reason
<Wizzup>
parazyd: we touched on it some after my msg
<uvos>
Wizzup: could be ram accuatlly
<uvos>
we dont touch the dram controller at all
<Wizzup>
right
<uvos>
the vendork kenrel might be changing things
<uvos>
depending on other clocks
<Wizzup>
yeah
<freemangordon>
Wizzup: what do you think about my suggestion re leste-config/postinst?
<uvos>
freemangordon: sec let me boot the thing
<freemangordon>
ok
<Wizzup>
freemangordon: sorry, how was it different from mine, maybe I missed it
<Wizzup>
20:10 < freemangordon> 1.one kernel package to rule them all
<Wizzup>
20:10 < freemangordon> 2. leste-config-n900 with postinst script that cats zImage+dtb and calls mkimage
<freemangordon>
if you don't have that, device may seem hung
<freemangordon>
Wizzup: yes
<Wizzup>
I suppose that could work too, but this allows potentially to have one without the other
<uvos>
freemangordon: its not that
<freemangordon>
uvos: ok
<uvos>
it dosent seam hung
<uvos>
it watchdog rebotos
<uvos>
*reboots
<freemangordon>
ah, ok
<freemangordon>
Wizzup: how's that different to your suggestion?
<freemangordon>
how do you know you run on n900?
<Wizzup>
freemangordon: I was suggesting to have extra pkgs in control file of our omap-linux debian/control
<freemangordon>
exactly, another package
<Wizzup>
freemangordon: like linux-image-n900
<Wizzup>
same repo, just another virtual
<Wizzup>
like we do with many things
<freemangordon>
and you may have one without the other
<Wizzup>
I don't think so
<freemangordon>
the same if it is in the config
<freemangordon>
ok
<Wizzup>
well yes you could *uninstall* linux-image-n900
<Wizzup>
that would uninstall the postinst
<Wizzup>
but that is more clear that is breaks things than leste-config-n900 imho
<freemangordon>
yeah, you have a point
<freemangordon>
Wizzup: so hildon-meta-n900 will depend on linux-image-n900?
<freemangordon>
IOW - which package will pull linux-image-n900?
<Wizzup>
freemangordon: right that is already the case now wrt meta
<freemangordon>
ok
<Wizzup>
so I will try that then
<freemangordon>
ok
<sicelo>
interesting - on Fremantle, it was said the bcm2048 integrated radio *requires* the bt to work. just re-read the short information sheet (https://pdf.dzsc.com/20090227/200902072254092347.pdf) and it states "FM system can operate independently from Bluetooth" ... can't wait to get my N900 fixed. maybe there's a way to make the FM transmitter work
inky_ has joined #maemo-leste
inky has quit [Read error: Connection reset by peer]
inky_ has quit [Read error: Connection reset by peer]
<sicelo>
s/transmitter/receiver/
<freemangordon>
it is the same chip
<freemangordon>
and I guess it needs FW to be loaded
inky_ has joined #maemo-leste
<Wizzup>
uvos: any idea why wl module is not loaded for droid3?
<sicelo>
the FW is for bt. you think the bt side must really be up?
<Wizzup>
uvos: seems kinda weird
<Wizzup>
freemangordon: do you want me to keep gdb attached to X to provide a backtrace when it crashes again?
<Wizzup>
freemangordon: although I guess it seems like kernel problem
<Wizzup>
freemangordon: or leak like you said
<freemangordon>
Wizzup: do you still see crashes?
<freemangordon>
or you mean that WARN()?
<Wizzup>
well what I pasted caused X to crash
lexik_ has joined #maemo-leste
<freemangordon>
ah
sunshavi_ has joined #maemo-leste
<freemangordon>
yeah, it is good to have backtrace
joerg has quit [Killed (tantalum.libera.chat (Nickname regained by services))]
joerg has joined #maemo-leste
ikmaak2 has joined #maemo-leste
<freemangordon>
maybe this can be handled gracefully
uvos__ has joined #maemo-leste
DPA- has joined #maemo-leste
sixwheel- has joined #maemo-leste
Newt-o has joined #maemo-leste
alex12161 has joined #maemo-leste
<Wizzup>
freemangordon: ok
xmn_ has joined #maemo-leste
Daanct12 has joined #maemo-leste
uvos__ has quit [Read error: Connection reset by peer]
inky_ has quit [*.net *.split]
n900 has quit [*.net *.split]
DPA has quit [*.net *.split]
amk has quit [*.net *.split]
lexik has quit [*.net *.split]
lel has quit [*.net *.split]
dos has quit [*.net *.split]
Newt-o_ has quit [*.net *.split]
bencoh has quit [*.net *.split]
ikmaak has quit [*.net *.split]
sixwheeledbeast has quit [*.net *.split]
Kabouik_ has joined #maemo-leste
sixwheel- is now known as sixwheeledbeast
amk has joined #maemo-leste
dos has joined #maemo-leste
xmn has quit [Ping timeout: 240 seconds]
peetah has quit [Ping timeout: 240 seconds]
Kabouik has quit [Ping timeout: 240 seconds]
xes has quit [Ping timeout: 240 seconds]
Danct12 has quit [Ping timeout: 240 seconds]
doc has quit [Ping timeout: 240 seconds]
uvos__ has joined #maemo-leste
doc has joined #maemo-leste
xmn has joined #maemo-leste
sicelo_ has joined #maemo-leste
sicelo_ has quit [Changing host]
sicelo_ has joined #maemo-leste
xes has joined #maemo-leste
alex1216 has quit [*.net *.split]
uvos has quit [*.net *.split]
sicelo has quit [*.net *.split]
dreamer has quit [*.net *.split]
Wikiwide has quit [*.net *.split]
L29Ah has quit [*.net *.split]
BenLand100 has quit [*.net *.split]
Langoor has quit [*.net *.split]
dsc_ has quit [*.net *.split]
sunshavi has quit [*.net *.split]
xes has quit [Signing in (xes)]
xes has joined #maemo-leste
sicelo_ is now known as sicelo
Daaanct12 has joined #maemo-leste
Langoor_ has joined #maemo-leste
Daanct12 has quit [Ping timeout: 256 seconds]
xmn_ has quit [Ping timeout: 256 seconds]
Newt-o has quit [Ping timeout: 256 seconds]
joerg has quit [Ping timeout: 256 seconds]
R0b0t1`` has quit [Remote host closed the connection]
R0b0t1`` has joined #maemo-leste
lexik_ has quit [Ping timeout: 256 seconds]
lexik has joined #maemo-leste
peetah has joined #maemo-leste
Newt-o has joined #maemo-leste
BenLand100 has joined #maemo-leste
joerg has joined #maemo-leste
BenLand100 has quit [Changing host]
BenLand100 has joined #maemo-leste
dsc_ has joined #maemo-leste
devrtz[m] has quit [Ping timeout: 240 seconds]
BlagovestPetrov[ has quit [Ping timeout: 268 seconds]
n900 has joined #maemo-leste
tvall has quit [Ping timeout: 260 seconds]
mint[m] has quit [Ping timeout: 250 seconds]
calebtheythem[m] has quit [Ping timeout: 250 seconds]
optix has quit [Ping timeout: 250 seconds]
M1peter10[m] has quit [Ping timeout: 252 seconds]
mighty17[m] has quit [Ping timeout: 252 seconds]
scops has quit [Ping timeout: 268 seconds]
wunderwungiel[m] has quit [Ping timeout: 245 seconds]
MartijnBraam[m] has quit [Ping timeout: 250 seconds]
alex12161 has quit [Ping timeout: 256 seconds]
bencoh has joined #maemo-leste
alex12161 has joined #maemo-leste
alex12161 has quit [Client Quit]
L29Ah has joined #maemo-leste
devrtz[m] has joined #maemo-leste
mint[m] has joined #maemo-leste
<Wizzup>
freemangordon: I think I will have to make those virtual packages in a different repo
calebtheythem[m] has joined #maemo-leste
optix has joined #maemo-leste
mighty17[m] has joined #maemo-leste
<freemangordon>
Wizzup: why is that?
<Wizzup>
freemangordon: scripts/packaging/builddep seems to create control files or something
<Wizzup>
it's overriding whatever else I have
<Wizzup>
and end result is I don't even get a .deb file for the other pkgs in my control file
<Wizzup>
dpkg-genchanges: warning: package linux-image-droid4 in control file but not in files list
<Wizzup>
dpkg-genchanges: warning: package linux-image-droid3 in control file but not in files list
<Wizzup>
dpkg-genchanges: warning: package linux-image-bionic in control file but not in files list
<Wizzup>
dpkg-genchanges: warning: package linux-image-n900 in control file but not in files list
MartijnBraam[m] has joined #maemo-leste
<Wizzup>
freemangordon: let me see if I am forgetting something else
wunderwungiel[m] has joined #maemo-leste
<freemangordon>
Wizzup: or, maybe do as I suggested
<Wizzup>
freemangordon: so they seem to call some custom bash create_package function that calls dpkg-gencontrol
<Wizzup>
freemangordon: right that is no different from the virtuals though right?
<uvos__>
[20:58] <Wizzup> uvos: any idea why wl module is not loaded for droid3?
<Wizzup>
I don't think leste-config is the right place for this
<uvos__>
its not?
<uvos__>
in what kernel
<Wizzup>
uvos__: not for me, is it loaded for you?
<Wizzup>
uvos__: just latest image
<freemangordon>
Wizzup: up to you, it is just that it will be easier
<Wizzup>
freemangordon: ok, let me take a few minutes to figure out what is easiest
BlagovestPetrov[ has joined #maemo-leste
<Wizzup>
so I was thinking of creating maemo-kernel-virtuals repos with just linux-image-n900 with depends on kernel package, but I'd really much rather have it in the kernel package
<Wizzup>
I could patch scripts/packaging/builddep
<Wizzup>
but it's not really pretty
<Wizzup>
brb
<freemangordon>
neither is creating yet another repo to hold just one package
<freemangordon>
unless by repo you mean git repo
<freemangordon>
not debian repo
<Wizzup>
I meant git repo yes
<Wizzup>
we can do it in leste-config it just feels a bit weird
<Wizzup>
but I don't mind having the postinst in there
<Wizzup>
I can just do that now I suppose, but still, we will need something to provide linux-image-droid4 and so on virtual packages still I think
<Wizzup>
unless we are just going to change all dependencies to linux-image-omap in hildon-meta etc
<Wizzup>
uvos__: btw I think reboots hang because one tty process becomes unkillable due to serial oops
<Wizzup>
uvos__: the S0 one
<freemangordon>
Wizzup: I think it makes sense to change all deps to linux-image-omap
<uvos__>
yes i know
<uvos__>
Wizzup: for some reason my wl12xx dose probe on d3
<uvos__>
but wifi dosent work at all
<Wizzup>
freemangordon: hmm ok
<uvos__>
can scann etc
<uvos__>
(also older kernel image)
<uvos__>
another think i notice
<uvos__>
is that d3 has alot more pixmap corruption
<Wizzup>
freemangordon: let's try that then
<freemangordon>
ok
<freemangordon>
Wizzup: how do you think, how critical is rotation on n900? IMO abook is with higher prio, no?
<Wizzup>
I think I agree yes
<freemangordon>
ok
<Wizzup>
yeah definitely
<uvos__>
x refuses to rotate right
<uvos__>
it dosent crash
<Wizzup>
yes
<uvos__>
ok
<freemangordon>
so VRFB will wait after abook
<uvos__>
then yeah
<freemangordon>
but, I think what I can spend some time on is PVR driver fences
<Wizzup>
having abook further along would help with our end of january conversations goals
<freemangordon>
for some reason current code sets the fence too early
<freemangordon>
Wizzup: yeah
<Wizzup>
I need to start pushing really hard on telepathy in the next two weeks or we won't make those
<Wizzup>
spent too much on kernel stuff relatively :p
<Wizzup>
too much time that is
<freemangordon>
I'll suspend kernel work until we have at least semi-usable abook
<freemangordon>
same here
<uvos__>
Wizzup: also on bringup devices that really dont matter :P
<uvos__>
(not that i blame you, its fun)
<uvos__>
i now know why wifi dosent work on my d3
<uvos__>
maserati-callibarte failed and hosed the firmware
<uvos__>
appearently it dosent work on d3 for some reason
<Wizzup>
uvos__: yeah
<Wizzup>
uvos__: ah I see, yeah, probably that never normally ran on mine because I used bionic sdcard initially
<freemangordon>
one more thing - maybe we shall make a freeze week. and if there are no critical bugs, all that is in -devel shall be pushed to stable
<freemangordon>
freeze like - no new stuff in -devel
<freemangordon>
as I am under the impression that -stable lags too much behind -devel
<freemangordon>
might be wrong though, didn;t compared
<uvos__>
well freezing devel is not the point of devel for us is it?
<Wizzup>
one of the reasons is we are making big changes
<freemangordon>
understood
<freemangordon>
but we are at the end of that
<freemangordon>
more or less
<uvos__>
i think another big(ish) problem is that stable has been less stable than devel in the past
<uvos__>
mostly because none of us use/test it
<freemangordon>
uvos__: another reason to make -stable equal to -devel
<Wizzup>
freemangordon: so do I make leste-config-n900 depend on u-boot-tools for mkimage?
<freemangordon>
mhm
<Wizzup>
k
<freemangordon>
uvos__: I am talking about very short freeze (week or so), to see if there are any critical bugs
<freemangordon>
I am not saying we shall stop development for that period :)
<freemangordon>
so, at the end of freeze, we push -devel to -stable and then build whatever is new in -devel
<Wizzup>
freemangordon: hmm leste-config does something weird with .leste files I am not sure if this will work...
<Wizzup>
parazyd: ping
<parazyd>
pong
M1peter10[m] has joined #maemo-leste
<Wizzup>
parazyd: hi, so
<Wizzup>
parazyd: I want to add a file that ends up in /etc/kernel/postinst.d
<Wizzup>
to create a uImage for the n900 and freemangordon would like it in leste-config
<Wizzup>
can I do that without making the file end in .leste and that kind of stuff?
<Wizzup>
I fear that might mess with run-parts
<Wizzup>
this would only be for leste-config-n900
<parazyd>
You can keep it in leste-config but then you have to install it by hand, not with the configfile infrastructure.
<Wizzup>
so just add another line to debian/leste-config-n900.install ?
<parazyd>
Otherwise, it does have to have the .leste suffix.
<parazyd>
Yeah
<Wizzup>
hmm
<parazyd>
Remember that debian/gen_displace will overwrite them
<Wizzup>
I am fine with whatever works really, so if you say that's the way to go then I'll do that
<parazyd>
And it also uses a wildcard, so I'm not exactly sure how to add another file.
<parazyd>
Probably if you just put it on top it'll work
<parazyd>
Why not make the uImage from kernel postinst?
<Wizzup>
if you can show me how I'll gladly do it
<Wizzup>
I can't figure out how to work with scripts/packaging/builddeb
<Wizzup>
it just does it's own thing and ignores everything else
<Wizzup>
or so it seems to me
<Wizzup>
I tried to add extra packages to the debian/control file of the kernel package, and then a debian/*.install file for it, it just gets ignored
<Wizzup>
and the .deb files are also not generated
<Wizzup>
I have a working postinst.d, I just need to be able to place it somewhere