http://bugzilla.opensuse.org/show_bug.cgi?id=1152627
Imobach Gonzalez Sosa <igonzalezsosa(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|yast2-maintainers(a)suse.de |igonzalezsosa(a)suse.com
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1151368http://bugzilla.suse.com/show_bug.cgi?id=1151368#c9
Nicolas Patricio Saenz Julienne <nsaenzjulienne(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--- Comment #9 from Nicolas Patricio Saenz Julienne <nsaenzjulienne(a)suse.com> ---
I spent some time looking at what is stopping us from adopting the downstream
kernel info. The main trouble is that the RPi firmware injects some custom DT
properties into the board's device tree, namely "linux,revision" and
"linux,serial". These don't have an official binding, which blocks us from
using them. One exists for serial numbers, but it's different, and there is no
consensus on how to deal with the revision.
Ideally if we ever find a way to pass this info into the device tree
generically we'd need to create a soc driver, which is the proper way of
exposing this information.
It'll take some coordination with the foundation as it's firmware dependent.
Overall I agree with Matthias, file a bug in the user-space library in order
for them to use standard Linux APIs.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1150790
Michal Filka <mfilka(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hagen.buliwyf(a)t-online.de
Flags| |needinfo?(hagen.buliwyf@t-o
| |nline.de)
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1150790http://bugzilla.suse.com/show_bug.cgi?id=1150790#c3
Michal Filka <mfilka(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mvidner(a)suse.com
Flags| |needinfo?(mvidner(a)suse.com)
--- Comment #3 from Michal Filka <mfilka(a)suse.com> ---
@Martin:
Can issue (2) from the Comment#1 be caused by disabling "Install recommended
packages"? Is it caused by e.g. separating translations for some packages into
own dedicated rpms?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1150790http://bugzilla.suse.com/show_bug.cgi?id=1150790#c1
--- Comment #1 from Michal Filka <mfilka(a)suse.com> ---
I see two issues described here
1) no graphical UI installed even when asked for (System Role: select "Desktop
with KDE Plasma")
2) when a display manager is installed manually the UI has broken translations
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1151368http://bugzilla.suse.com/show_bug.cgi?id=1151368#c8
Matthias Brugger <mbrugger(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
Assignee|kernel-maintainers(a)forge.pr |mbrugger(a)suse.com
|ovo.novell.com |
--- Comment #8 from Matthias Brugger <mbrugger(a)suse.com> ---
I think this is rather something that the python-RPi.GPIO would need to fix. A
quick look on the code gives me the feeling that this is rather trivial [1].
[1]
https://sourceforge.net/p/raspberry-gpio-python/code/ci/default/tree/source…
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1148679http://bugzilla.suse.com/show_bug.cgi?id=1148679#c3
Michal Filka <mfilka(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(mfilka(a)suse.com) |needinfo?(jeriveramoya@suse
| |.com)
--- Comment #3 from Michal Filka <mfilka(a)suse.com> ---
There were quite some changes in past weeks as we switched to completely new
backend in yast2 network. Could you pls verify if the bug is still valid?
--
You are receiving this mail because:
You are on the CC list for the bug.