public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: chuck gelm <chuck@gelm.net>
To: linux-newbie@vger.kernel.org
Cc: Rajat Jain <rajat.noida.india@gmail.com>
Subject: Re: How to change PCI Configuration space?
Date: Tue, 30 Aug 2005 22:30:38 -0400	[thread overview]
Message-ID: <4315164E.905@gelm.net> (raw)
In-Reply-To: <b115cb5f0508301805528e4bf0@mail.gmail.com>

Rajat Jain wrote:
> On 8/31/05, chuck gelm <chuck@gelm.net> wrote:
> 
>>Rajat Jain wrote:
>>
>>>Hi List,
>>>
>>>I want to change the PCI Configuration space of a particular device in
>>>my system. I am trying to use the "pcitweak" utility to do so, but am
>>>not suceeding. I would appreciate if some body could provide me any
>>>pointers in how to do so.
>>>
>>>In this case, I want to change the value at offset 64:
>>>
>>>$ pcitweak -r 5:9:1 64
>>>0x01000001                 //original value
>>>
>>>$ pcitweak -w 5:9:1 64 0x02000002      //new value
>>>
>>>$ pcitweak -r 5:9:1 64
>>>0x01000001                //no change?
>>>
>>>TIA,
>>>
>>>Rajat Jain
>>
>>Dear Rajat Jain:
>>
>> 'man pcitweak' indicates that it requires root privileges.
>>the '$' prompt in your console indicates 'user' privileges.
>>My 'root' prompt is a '#'.
>>I suggest that you do not have 'root' privileges when
>>executing  a '-w' (write) command.
>>
>>HTH, Chuck
>>
>>"Pcitweak  is  a  utility  that  can  be used to examine or
>> change registers in the PCI configuration space.  On  most
>> platfoms pcitweak can only be run by the root user."
>>
> 
> 
> 
> Un ... I'm sorry ... I put that "$" prompt manually here in this mail.
> I AM the root and working on the "#" prompt. I would appreciate if
> somebody can tell me any other commands than "pcitweak" and "setpci"
> to change PCI configuration space.
> 
> Thanks & Regards,
> 
> Rajat Jain

Hi, Rajat Jain:

  Sorry, I cannot help.  Just for fun, I used pcitweak, scanpci, lspci,
and 'cat /proc/pci' and looked at my two rtl8139 ethernet cards.  I
think I found that they have 256 bytes of memory; one card uses memory
0x3e014000 - 0x3e140ff or 0x100 bytes.
(cat /proc/pci |grep -A 1 -B 4 ealtek)

  pcitweak read 32 bits (4 bytes) so
pcitweak 0:9:0 -r 0
  would show bytes offset 0, 1, 2, & 3.

pcitweak 0:9:0 -r[-w] 64 [value]
  would read[write] bytes offset 64, 65, 66, 67
  or 0x100, 0x101, 0x102, 0x103
  which is undefined.  There might be no RAM memory at byte offset 64.

  I also used pcitweak 0:9:0 -r 4096, which I assume is outside the
configuration space of my pci device, but pcitweak dutifully displayed
output.  :-|

Hopefully you are not writing to ROM. :-|

Good luck,
Chuck


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2005-08-31  2:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30  4:47 How to change PCI Configuration space? Rajat Jain
2005-08-30 13:11 ` [Pcihpd-discuss] " Matthew Wilcox
2005-08-30 16:22 ` chuck gelm
2005-08-31  1:05   ` Rajat Jain
2005-08-31  2:30     ` chuck gelm [this message]
2005-08-31  2:47 ` chuck gelm

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=4315164E.905@gelm.net \
    --to=chuck@gelm.net \
    --cc=linux-newbie@vger.kernel.org \
    --cc=rajat.noida.india@gmail.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