linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sylvain Munaut <tnt@246tNt.com>
To: Mark Chambers <markc@mail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC52xx: sysfs failure on adding new device driver
Date: Thu, 09 Jun 2005 13:32:07 +0200	[thread overview]
Message-ID: <42A828B7.4030305@246tNt.com> (raw)
In-Reply-To: <002201c56ce5$561a6c50$0301a8c0@chuck2>

Hi Mark

Mark Chambers wrote:
>>I'm working on an MPC52xx SPI device driver using one of the PSC. 
>>However, when I call driver_register() I get a failure (-17, EEXISTS)
>>with a traceback (posted below).
> 
> 
> Hey Grant,
> 
> This sounds exactly like a problem I had with PSC with devfs.  I posted
> a patch here on 5/27, I bet you'll find it's a similar problem.  
> 
> (Let me know if you don't have access to that patch, I'll forward you my
> copy)

Don't think so. Your patch applies to the 2.4 while Grant problem is 
specific to the way the different functions of PSCs are handled to work 
the 2.6 ppc_sys model.

btw, if not yet integrated you should send your patch to Wolfang, he's 
the one maintaining that tree.


	Sylvain

  reply	other threads:[~2005-06-09 11:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 23:51 MPC52xx: sysfs failure on adding new device driver Grant Likely
2005-06-09 11:21 ` Mark Chambers
2005-06-09 11:32   ` Sylvain Munaut [this message]
2005-06-09 13:55     ` Wolfgang Denk
2005-06-09 15:28       ` Mark Chambers
2005-06-09 18:34         ` Grant Likely
2005-06-09 11:28 ` Sylvain Munaut
2005-06-09 14:54   ` Grant Likely
2005-06-09 15:20     ` Kumar Gala
2005-06-09 18:48       ` Grant Likely
2005-06-10 14:09         ` Sylvain Munaut
2005-06-10 16:06           ` Grant Likely
2005-06-13 19:08           ` Grant Likely

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=42A828B7.4030305@246tNt.com \
    --to=tnt@246tnt.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=markc@mail.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;
as well as URLs for NNTP newsgroup(s).