<Wizzup>
well the last one is clearly wrong I think
System_Error has quit [Remote host closed the connection]
<Wizzup>
fixed
System_Error has joined #maemo-leste
<freemangordon>
osso-abook is ok
<Wizzup>
yes
<Wizzup>
btw, I found the redpill mode in h-a-m as well as the flags for system upgrades
<Wizzup>
- system-update
<Wizzup>
Specifying this flag will tell the AM that this is a meta package that controls operating system updates. The AM will adjust some parts of its UI.
<freemangordon>
yeah, redpill mode :)
<Wizzup>
ideally we would have 'red pill' mode for updates but not for regular pkg installs
<freemangordon>
yep, we can use it
<freemangordon>
system update mode that is
<freemangordon>
I have to recall what did I do back the when I was maintaining cssu-thumb
<Wizzup>
I think we could just add this flag to hildon-meta
<Wizzup>
it would just get a bit annoying every time we update it :)
<Wizzup>
or maybe we make some other pkg that we update less often
<freemangordon>
I don;t understand what I am required to do in terms of "Instead: interrupts and say which interrupt is where." etc
<freemangordon>
Wizzup: ^^^
<freemangordon>
if you understand, please translate it it me
ceene has quit [Ping timeout: 252 seconds]
Livio has quit [Ping timeout: 264 seconds]
<Wizzup>
sorry, don't really know
<tmlind>
freemangordon: best to set it up as a standard yaml binding which uses interrupts property
<tmlind>
freemangordon: and simplify the description to say something like "Add the DT binding for the audio-codec headset detection interrupts."
<tmlind>
i think the yaml binding is very simple as no non-standard properties are used
<freemangordon>
tmlind: ok, thanks, but there is already txt bindings
<freemangordon>
so I am just adding
<freemangordon>
I asked Krzysztof if I should convert to yaml, no reply :)
<freemangordon>
so, will just send v2 of the series with whatever I did and will see
<freemangordon>
at least I am training my patch-sending-fu :D
<tmlind>
freemangordon: i suggest first patch convert to yaml, second patch add interrupt
<tmlind>
and run make dt_binding_check or whatever the command is on the yaml binding as after all that's the whole idea of yaml bindings :)
<freemangordon>
ok, but converting to yaml can be done in follow-up patch, no?
<tmlind>
sure if the addition of interrupt is just a minimal change
<freemangordon>
it is
<tmlind>
ok
<freemangordon>
3 lines or something
<tmlind>
ok
<freemangordon>
you're in the list, will see in 5 minutes
<tmlind>
ok, see Documentation/devicetree/bindings/power/supply/cpcap-battery.yaml for an example of how the interrupts end up looking like
<freemangordon>
I saw it, but this is yaml
<freemangordon>
currntly it is not
<tmlind>
right but that's what it will end up being like eventually, i think that's the comment "this goes to the interrupts description" part relates to
<tmlind>
so you can try to make the yaml conversion easy by not trying to add non-standard stuff to the text binding first :)
<freemangordon>
well, I send v2 of the series, lets see
<freemangordon>
*sent
<freemangordon>
lets hope this time requirements will be clearly stated
mkfx has joined #maemo-leste
<tmlind>
freemangordon: looks good to me :)
<freemangordon>
Reviewed-by? :)
<tmlind>
can't deal with my email right now, maybe later..
<freemangordon>
BTW, I got ack from Morimoto-san for the patch I was thinking will be very hard to push upstream, lets see if it will be merged
<arno11>
Wizzup: still the same gconf/dbus errors in console :(
<Wizzup>
arno11: this is with what?
<Wizzup>
oh the image?
<Wizzup>
just let it build and let's see
<Wizzup>
I am not convinced the gconf errors were ever not there
<Wizzup>
in the console I mean
<Wizzup>
we don't have X, so yeah
<arno11>
yes i meant the image, ok @ X
<Wizzup>
You can see in the log it is still doing its thing
<Wizzup>
(gconftool-2:26652): GConf-␛[1;33mWARNING␛[0m **: ␛[34m16:11:26.887␛[0m: Client failed to connect to the D-BUS daemon:
<Wizzup>
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
<Wizzup>
Attached schema `/schemas/apps/osso/apps/controlpanel/groups' to key `/apps/osso/apps/controlpanel/groups'
<Wizzup>
Installed schema `/schemas/apps/osso/apps/controlpanel/groups' for locale `C'
<Wizzup>
Attached schema `/schemas/apps/osso/apps/controlpanel/group_ids' to key `/apps/osso/apps/controlpanel/group_ids'
<Wizzup>
Installed schema `/schemas/apps/osso/apps/controlpanel/group_ids' for locale `C'
<arno11>
yes i saw it
<Wizzup>
I am currently fairly convinced the problem is with me switching out the 32 bit image builder
<Wizzup>
I did that many months ago and I think this coincides with the reported issues
<arno11>
ok
<Wizzup>
when it's done I will dd it to my test droid and report back
<arno11>
cool
<tmlind>
freemangordon: hey that's great to hear about the morimoto san
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
Anasko has joined #maemo-leste
_fab has quit [Quit: _fab]
xmn_ has joined #maemo-leste
xmn has quit [Ping timeout: 260 seconds]
Livio has joined #maemo-leste
<sicelo>
Wizzup: seems the N900's kernel regression is affecting everything on spi bus, including the wireless :p