Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@embeddedalley.com>
To: Gilad Rom <gilad@romat.com>
Cc: linux-mips@linux-mips.org
Subject: Re: תשובה: תשובה: Au1500 Chip Select
Date: Wed, 24 Nov 2004 23:54:58 -0800	[thread overview]
Message-ID: <41A58FD2.1020100@embeddedalley.com> (raw)
In-Reply-To: <20041125073158.98A11EB2A9@mail.romat.com>

Gilad Rom wrote:
> The device is a simple ALTERA chip, used for testing (for the mean time).
> I need to make sure that I can access it, and simply read data from it.
> Here's my question: Let's say I assign 0x1000 as the address portion (CSBA)
> Of MEM_STADDR1. What address should I mmap after that?

I don't have the spec in front of me. It's whatever 0x1000 in the CS 
translates to as the physical address.

Pete

> (Using mmap only for initial development, Once I realize all I need
> To do I'll write a driver).
> 
> Thanks,
> Gilad.
> 
> -----הודעה מקורית-----
> מאת: linux-mips-bounce@linux-mips.org
> [mailto:linux-mips-bounce@linux-mips.org] בשם Pete Popov
> נשלח: Thursday, November 25, 2004 9:23 AM
> אל: Gilad Rom
> עותק: linux-mips@linux-mips.org
> נושא: Re: תשובה: Au1500 Chip Select
> 
> Gilad Rom wrote:
> 
>>Well, what I did so far was setup mem_stcfg1/mem_staddr1. 
>>What I'm having trouble with is, what values do I need to Set in 
>>mem_staddr1,
> 
> 
> Depends on the device attached to that CS and the physical address you want
> to assign to it.
> 
> 
>>and then, how do I access
>>That memory (mmap? Driver?).
> 
> 
> Driver would be better.
> 
> Pete
> 
> 
>>Thanks.
>>Gilad.
>>
>>-----הודעה מקורית-----
>>מאת: linux-mips-bounce@linux-mips.org
>>[mailto:linux-mips-bounce@linux-mips.org] בשם Pete Popov
>>נשלח: Wednesday, November 24, 2004 7:58 PM
>>אל: Gilad Rom
>>עותק: linux-mips@linux-mips.org
>>נושא: Re: Au1500 Chip Select
>>
>>Gilad Rom wrote:
>>
>>
>>
>>>Hello,
>>>
>>>I am trying to implement a simple program which Will be used to 
>>>communicate with an I/O peripheral Over CS1 (Chip select 1) of the 
>>>au1500.
>>
>>
>>I'm not sure I understand what you're trying to do. The chip select is 
>>setup by the boot loader or kernel, and you don't touch it anymore. 
>>The CS will get asserted/deasserted based on the addresses you're trying
> 
> to access.
> 
>>
>>>Has anyone ever attempted this? Could someone Point me to some sample 
>>>code, perhaps? I am grepping Through the kernel, yet having trouble 
>>>locating Chip-select specific code for reference.
>>
>>
>>Again, what sort of an example are you looking for?  Setting up a chip 
>>select on the Au1x is nothing more than writing the appropriate values 
>>to the 3 chip select registers. Then you're done.
>>
>>Pete
>>
>>
>>
>>
> 
> 
> 
> 
> 
> 

      parent reply	other threads:[~2004-11-25  7:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24 14:32 Au1500 Chip Select Gilad Rom
2004-11-24 14:32 ` Gilad Rom
2004-11-24 17:57 ` Pete Popov
2004-11-25  7:12   ` תשובה: " Gilad Rom
2004-11-25  7:12     ` Gilad Rom
2004-11-25  7:23     ` Pete Popov
2004-11-25  7:32       ` תשובה: " Gilad Rom
2004-11-25  7:32         ` Gilad Rom
2004-11-25  7:54         ` Pete Popov [this message]

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=41A58FD2.1020100@embeddedalley.com \
    --to=ppopov@embeddedalley.com \
    --cc=gilad@romat.com \
    --cc=linux-mips@linux-mips.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