Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Martin Michlmayr <tbm@cyrius.com>,
	linux-mips@linux-mips.org,
	Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
Subject: Re: SGI O2 meth: missing sysfs device symlink
Date: Tue, 22 May 2007 23:51:30 -0400	[thread overview]
Message-ID: <4653BA42.3060104@gentoo.org> (raw)
In-Reply-To: <20070522110956.GB29118@linux-mips.org>

Ralf Baechle wrote:
> On Mon, May 21, 2007 at 04:47:26PM +0100, Ralf Baechle wrote:
> 
> Below patch is meant to cure the problem.  It's against HEAD but should
> apply to somewhat older problems as well.
> 
> I appreciate testing asap so I can try to still push this upstream
> for 2.6.22.
> 
> Thanks,
> 
>   Ralf
> 

Didn't test on 2.6.22 (yet), but 2.6.21.1 works:

# ls -ld /sys/class/net/*{,/device}
drwxr-xr-x 3 root root 0 May 22 18:19 /sys/class/net/eth0/
lrwxrwxrwx 1 root root 0 May 22 18:19 /sys/class/net/eth0/device -> 
../../../devices/platform/meth/
drwxr-xr-x 3 root root 0 May 22 18:19 /sys/class/net/lo/


Btw, If we wanted to protect meth from the speculative execution issues of the 
R10000 processor, what's the right way for that?  I believe IP28 used a special 
type of buffer for protecting Seeq from the DMA wonkiness that occurs, but I got 
the indication that Meth would need a different approach.


--Kumba

-- 
Gentoo/MIPS Team Lead

"Such is oft the course of deeds that move the wheels of the world: small hands 
do them because they must, while the eyes of the great are elsewhere."  --Elrond

  parent reply	other threads:[~2007-05-23  3:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1178743456.15447.41.camel@scarafaggio>
     [not found] ` <20070516151939.GH19816@deprecation.cyrius.com>
     [not found]   ` <20070516160313.GA3409@bongo.bofh.it>
     [not found]     ` <50621.192.168.2.50.1179383217.squirrel@eppesuigoccas.homedns.org>
2007-05-17 15:16       ` SGI O2 meth: missing sysfs device symlink Martin Michlmayr
2007-05-21 15:47         ` Ralf Baechle
2007-05-22 11:09           ` Ralf Baechle
2007-05-22 11:41             ` Giuseppe Sacco
2007-05-22 12:01               ` sknauert
2007-05-22 12:28                 ` Ralf Baechle
2007-05-22 13:32                   ` sknauert
2007-05-22 15:18                     ` Thiemo Seufer
2007-05-22 16:46                       ` Cross-Compile difficulties sknauert
2007-05-22 17:32                         ` Geert Uytterhoeven
2007-05-22 22:44                           ` sknauert
2007-05-22 23:26                             ` Carlos Munoz
2007-05-23  3:42                             ` Kumba
2007-05-23 17:41                               ` sknauert
2007-05-23  6:12                             ` Geert Uytterhoeven
2007-05-22 13:02                 ` SGI O2 meth: missing sysfs device symlink Thiemo Seufer
2007-05-22 12:13               ` Giuseppe Sacco
2007-05-22 13:00                 ` Ralf Baechle
2007-05-23 11:45                 ` Giuseppe Sacco
2007-05-24 11:47                   ` Ralf Baechle
2007-05-23  3:51             ` Kumba [this message]
2007-05-23  8:37               ` Ralf Baechle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4653BA42.3060104@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=giuseppe@eppesuigoccas.homedns.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=tbm@cyrius.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox