LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "John Linn" <John.Linn@xilinx.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: Problems in fixup_device function
Date: Thu, 6 Mar 2008 12:21:46 -0700	[thread overview]
Message-ID: <20080306192149.4A0A9708064@mail119-dub.bigfish.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 593 bytes --]

I've added some code to virtex_device_fixup and am seeing some strange
side affects.  I've added code to read from an iic device and populate
the mac address including ioremap.  The code works fine, but the side
affects are not fine.

 

Anyone have any experience here?

 

I see the loops_per_jiffy getting hosed like there is some bad code, but
I can't track it down.  It moves around badly, like it can come and go
with printk additions or deletions.

 

I don't know enough about the stack and Linux to know if there could be
a problem there.

 

Thanks,

John


[-- Attachment #2: Type: text/html, Size: 8016 bytes --]

             reply	other threads:[~2008-03-06 19:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 19:21 John Linn [this message]
2008-03-06 19:38 ` Problems in fixup_device function Grant Likely
2008-03-06 19:40   ` John Linn

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=20080306192149.4A0A9708064@mail119-dub.bigfish.com \
    --to=john.linn@xilinx.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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