[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#706476: marked as done ([x86] GPIOs not exposed to userland)

Your message dated Sun, 01 Jul 2018 01:37:43 +0100
with message-id <d2b51f6b4367f8398bbe9ace8a756af707bfa5bc.camel@decadent.org.uk>
and subject line Re: [x86] GPIOs not exposed to userland
has caused the Debian Bug report #706476,
regarding [x86] GPIOs not exposed to userland
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
706476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706476
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-3.2.0-4-486
Severity: important


discovered from another debian bugreport that pc-engines systems can be
upgraded to more recent firmware and work with linux-image-3.2.0-4-486
(which is great!) and also discovered that the geodewdt kernel module
has been compiled, which is also great (as it's missing from the 2.6.32
debian kernel builds)

however what's not so great is that the GPIO 5535 kernel driver has been
left out, and it is a requirement for the project.  as native builds on
500mhz AMD Geodes take absolutely forever it would be nice if this could
be corrected. kernel option is GPIO_CS5535


-- System Information:
Debian Release: 6.0.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
Version: 4.3.3-6

On Thu, 2 May 2013 17:01:18 +0100 Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> ok, it turns out that CONFIG_SYSFS_GPIO is "safe", because you have to
> explicitly take action in order to make GPIO accessible (export).
> following the instructions here was easy to do:
> https://sites.google.com/site/bifferboard/Home/gpio
> 
> so, basically, CONFIG_SYSFS_GPIO could be switched on (as built-in).

This was enabled in the above version.

Ben.

-- 
Ben Hutchings
Q.  Which is the greater problem in the world today,
    ignorance or apathy?
A.  I don't know and I couldn't care less.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: