Send buglog mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
        [EMAIL PROTECTED]

You can reach the person managing the list at
        [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:

   1. [Bug 206] New: Disallow setting of overvoltage via pcf50606
      sysctl    interface ([EMAIL PROTECTED])
   2. [Bug 206] New: Disallow setting of overvoltage via pcf50606
      sysctl    interface ([EMAIL PROTECTED])
   3. [Bug 206] Disallow setting of overvoltage via pcf50606 kernel
      driver ([EMAIL PROTECTED])
   4. [Bug 206] Disallow setting of overvoltage via pcf50606 kernel
      driver ([EMAIL PROTECTED])
   5. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=206

           Summary: Disallow setting of overvoltage via pcf50606 sysctl
                    interface
           Product: OpenMoko
           Version: current svn head
          Platform: Neo1973
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: kernel
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [EMAIL PROTECTED]


currently there are no kernel-enforced limits for the voltage regulator
settings. This means that [root] user can set overvoltages on various parts of
the system.

We need something like a table of maximum voltages (for each system revision).

Ideally this should become part of a platform_device private data structure,
something like (per-regulator):

struct {
     u_int16_t max_voltage;
     u_int16_t min_voltage;
     unsigned int flags;      /* such as F_DEFAULT_ON */
     char *name;
};

the voltage setting functions should then not only respect the limits by
pcf50606 hardware, but the limits present in that structure.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You reported the bug, or are watching the reporter.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=206

           Summary: Disallow setting of overvoltage via pcf50606 sysctl
                    interface
           Product: OpenMoko
           Version: current svn head
          Platform: Neo1973
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: kernel
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [EMAIL PROTECTED]


currently there are no kernel-enforced limits for the voltage regulator
settings. This means that [root] user can set overvoltages on various parts of
the system.

We need something like a table of maximum voltages (for each system revision).

Ideally this should become part of a platform_device private data structure,
something like (per-regulator):

struct {
     u_int16_t max_voltage;
     u_int16_t min_voltage;
     unsigned int flags;      /* such as F_DEFAULT_ON */
     char *name;
};

the voltage setting functions should then not only respect the limits by
pcf50606 hardware, but the limits present in that structure.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=206

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Disallow setting of         |Disallow setting of
                   |overvoltage via pcf50606    |overvoltage via pcf50606
                   |sysctl interface            |kernel driver





------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You reported the bug, or are watching the reporter.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=206

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Disallow setting of         |Disallow setting of
                   |overvoltage via pcf50606    |overvoltage via pcf50606
                   |sysctl interface            |kernel driver





------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.

All of these bugs are in the NEW state, and have not been touched
in 7 days or more.  You need to take a look at them, and 
decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
    else.  (Hint: if you don't know who to reassign it to, make sure that
    the Component field seems reasonable, and then use the "Reassign bug to
    owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):

    
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL 
PROTECTED]

Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.

Appended below are the individual URLs to get to all of your NEW bugs that 
haven't been touched for a week or more.

You will get this message once a day until you've dealt with these bugs!

  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=70
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=137
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=143
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=192



--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to