Re: demuxing irqs

2008-09-14 Thread Jon Smirl
How do the virq numbers get assigned?
What do I pass into request_irq when I use one of these pins?

The gpio device...
gpio_wkup: [EMAIL PROTECTED] {
compatible = 
fsl,mpc5200b-gpio-wkup,fsl,mpc5200-gpio-wkup;
reg = 0xc00 0x40;
interrupts = 0x1 0x8 0x0 0x0 0x3 0x0;
interrupt-parent = mpc5200_pic;
gpio-controller;
#gpio-cells = 4;
};

use of a gpio from the device...
[EMAIL PROTECTED] {
compatible = digispeaker,gpio-ir;

gpios = gpio_wkup 0 0 1 0;
};


0 - gpio number in the device
0 - enable open drain
1 - class of interrupt, normal or wakeup
0 - type of interrupt, rising, falling, both, pulse


-- 
Jon Smirl
[EMAIL PROTECTED]
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: Device treee syntax for expanding mpc5200 gpios

2008-09-14 Thread David Gibson
On Fri, Sep 12, 2008 at 04:43:22PM -0400, Jon Smirl wrote:
 I need to implement some more of the mpc5200's gpio capabilities.
 
 Right now we have:
 gpios = gpio_wkup 0 0;
 first cell is index into the bank, and second is unused.
 
 What do we need to fully describe a mpc5200 gpio?
 
 1) open drain: 1 enable
 2) interrupt: 0 no int, 1 simple, 2 wakeup, 3 both
 3) interrupt type: 0 any transition, 1 rising, 2 falling, 3 pulse

Maybe I'm misunderstanding the situation, but 2 and maybe 3 look more
like configuration than something inherent to the hardware setup.
Couldn't different drivers potentially choose different interrupt
modes depending on their needs?  Remember the device tree describes
the hardware, not how it's used.

-- 
David Gibson| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au  | minimalist, thank you.  NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: [PATCH]: [MPC5200] Add ATA DMA support

2008-09-14 Thread Grant Likely
On Wed, Aug 13, 2008 at 3:07 AM, Tim Yamin [EMAIL PROTECTED] wrote:
 On Wed, Aug 13, 2008 at 7:11 AM, Grant Likely [EMAIL PROTECTED] wrote:
 Sounds good to me.  You will get more testers that way.  I can pick it
 up for -next if everything else looks good.

 Here are the new patches; tested against 2.6.27-rc3.

Hi Tim,

I finally got a chance to try out your patches on my lite5200 board.
Unfortunately, I wasn't able to get it to work easily.  I'm very early
in the debugging this issue, but I thought I'd send you my results in
case you've seen it before.  I've tried this with both an STEC 1GB CF
and a Transcend Ultra industrial 1GB CF card.

When the patch is enabled, Linux boots to the point of probing the ATA
bus.  The first attempt to probe uses UDMA/33 which ends in a timeout.
 Second attempt limits it to UDMA/25 which also times out.  Third
attempt falls back to PIO4 mode which then succeeds and the boot
process continues.  I haven't dug into the details of MPC5200 UDMA
support yet, but I'd like to know if you have any ideas.

Cheers,
g.

Full boot log below:

U-Boot 1.3.4-rc2 (Aug  1 2008 - 14:11:20)

CPU:   MPC5200B v2.2, Core v1.4 at 462 MHz
   Bus 132 MHz, IPB 132 MHz, PCI 33 MHz
Board: Freescale Lite5200B
I2C:   85 kHz, ready
DRAM:  256 MB
FLASH: 32 MB
PCI:   Bus Dev VenId DevId Class Int
00  1a  1057  5809  0680  00
In:serial
Out:   serial
Err:   serial
Net:   FEC ETHERNET
IDE:   Bus 0: OK
  Device 0: Model: TRANSCEND Firm: 20070418 Ser#: 0   521143E8
Type: Hard Disk
Capacity: 971.5 MB = 0.9 GB (1989792 x 512)
  Device 1: Model:  Firm:  Ser#:
Type: # 1F #
Capacity: not available
Hit any key to stop autoboot:  0
= boot
Using FEC ETHERNET device
TFTP from server 192.168.0.200; our IP address is 192.168.0.70
Filename 'mpc5200/uImage.gcl'.
Load address: 0x40
Loading: #
 #
done
Bytes transferred = 1376680 (1501a8 hex)
Using FEC ETHERNET device
TFTP from server 192.168.0.200; our IP address is 192.168.0.70
Filename 'mpc5200/lite5200b.dtb'.
Load address: 0x3f
Loading: #
done
Bytes transferred = 8192 (2000 hex)
## Booting kernel from Legacy Image at 0040 ...
   Image Name:   Linux-2.6.27-rc6-00038-gc03fbd9
   Created:  2008-09-14   3:16:24 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:1376616 Bytes =  1.3 MB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Flattened Device Tree blob at 003f
   Booting using the fdt blob at 0x3f
[0.00] Using lite5200 machine description
[0.00] Linux version 2.6.27-rc6-00038-gc03fbd9
([EMAIL PROTECTED]) (gcc version 4.0.0 (DENX ELDK 4.1 4.0.0)) #465 Sat
Sep 13 21:15:54 MDT 2008
[0.00] PCI host bridge /[EMAIL PROTECTED] (primary) ranges:
[0.00]  MEM 0x8000..0x9fff -
0x8000 Prefetch
[0.00]  MEM 0xa000..0xafff -
0xa000
[0.00]   IO 0xb000..0xb0ff - 0x
[0.00] Zone PFN ranges:
[0.00]   DMA  0x - 0x0001
[0.00]   Normal   0x0001 - 0x0001
[0.00] Movable zone start PFN for each node
[0.00] early_node_map[1] active PFN ranges
[0.00] 0: 0x - 0x0001
[0.00] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 65024
[0.00] Kernel command line: root=/dev/nfs rw
nfsroot=192.168.0.200:/home/srv/nfs/gdc/lite5200-1
ip=192.168.0.70:192.168.0.200:192.168.0.1:255.255.255.0:lite5200-1:eth0:off
console=ttyPSC0,115200
[0.00] MPC52xx PIC is up and running!
[0.00] PID hash table entries: 1024 (order: 10, 4096 bytes)
[0.00] clocksource: timebase mult[79364d9] shift[22] registered
[0.000194] console [ttyPSC0] enabled
[0.120005] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[0.128964] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[0.166748] Memory: 256572k/262144k available (2740k kernel code,
5272k reserved, 108k data, 108k bss, 168k init)
[0.177420] SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0,
CPUs=1, Nodes=1
[0.185307] Calibrating delay loop... 65.79 BogoMIPS (lpj=131584)
[0.280159] Mount-cache hash table entries: 512
[0.288690] net_namespace: 288 bytes
[0.293054] NET: Registered protocol family 16
[0.314694] PCI: Probing PCI hardware
[0.319804] bus: 00 index 0 io port: [ff, 100c03f2000]
[0.325470] bus: 00 index 1 mmio: [80009fff, a0b]
[0.331081] bus: 00 index 2 mmio: [a000afff, a4b]
[0.336808] DMA: MPC52xx BestComm driver
[0.341125] DMA: MPC52xx BestComm engine @f0001200 ok !
[0.355586] SCSI subsystem initialized
[0.376841] NET: Registered protocol family 2
[0.415732] 

Re: demuxing irqs

2008-09-14 Thread Jon Smirl
YDL has pretty much followed the Red Hat distribution so focusing on
learning how that works -- the RH manual can be directly downloaded from
Red Hat -- should be the only thing one needs besides typical training
available regarding good best practice strategies for nearly any
Linux/Unix family of systems in applying System Administration
strategies.  Developing programming skills in the various computer
languages are standard academic skills one can develop independently
or via college.

Of course after all that there remains the necessity of learning and
applying what YDL is really great for -- mastery of the Cell via
advanced mathematics.  Now that is something which only YDL can allow
you do exclusively and well.

On Wed, Jul 16, 2008 at 5:40 PM, Posey, Jake E  
[EMAIL PROTECTED] wrote:
 Are there any training courses available for YDL?



 Thanks,

 Jake





 ___
 yellowdog-general mailing list
 yellowdog-general@lists.terrasoftsolutions.com
 http://lists.terrasoftsolutilor_bg = "FF";
google_color_link = "006792";
google_color_url = "006792";
google_color_text = "00";
//-->







demuxing irqs
Jon Smirl


Re: demuxing irqs
Roland Dreier


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Roland Dreier


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Jon Smirl



Re: demuxing irqs
Jon Smirl
 


Re: demuxing irqs
Jon Smirl

















 






  
  





Reply via email to



  
  





 
 








 












demuxing irqs
Jon Smirl


Re: demuxing irqs
Roland Dreier


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Roland Dreier


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Jon Smirl



Re: demuxing irqs
Jon Smirl
 


Re: demuxing irqs
Jon Smirl

Re: demuxing irqs
Anton Vorontsov

Re: demuxing irqs
Jon Smirl



















 






  
  





Reply via email to



  
  





 
 








 












demuxing irqs
Jon Smirl


Re: demuxing irqs
Roland Dreier


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Roland Dreier


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Jon Smirl



Re: demuxing irqs
Jon Smirl
 


Re: demuxing irqs
Jon Smirl

Re: demuxing irqs
Anton Vorontsov

Re: demuxing irqs
Jon Smirl

Re: demuxing irqs
Anton Vorontsov

Re: demuxing irqs
Jon Smirl

Re: demuxing irqs
Anton Vorontsov

Re: demuxing irqs
Jon Smirl

Re: demuxing irqs
Scott Wood

Re: demuxing irqs
Jon Smirl

Re: demuxing irqs
Anton Vorontsov


























 






  
  





Reply via email to



  
  





 
 







Re: Device treee syntax for expanding mpc5200 gpios

2008-09-14 Thread Jon Smirl
On Wed, Jul 16, 2008 at 07:52:54PM +, Derick Centeno wrote:
 I recall a discussion regarding gfortran sometime ago.  I'm sure it
 can be installed by using yum.  The simplest way is probably:
 
 #yum install gfortran*
 
 You can make sure it's available by:
 
 #yum info gfortran* or
 
 #yum search gfortran*

The current package containing gfortran in YDL6 is 
gcc-gfortran-4.1.1-52.ydl.1

I never attempted to compile gfortran from the sources.
However I did compile g95 (whicx1 0xe 0x0;
cell 1 = class critical, normal, sdma
cell 2 = number
cell 3 = level

Cell 3 is probably not needed in the existing definitions.

GPIO wake up interrupts come in on two different hardware interrupts
depending if they are normal or wake up.

gpio_wkup: [EMAIL PROTECTED] {
compatible = 
fsl,mpc5200b-gpio-wkup,fsl,mpc5200-gpio-wkup;
reg = 0xc00 0x40;
interrupts = 0x1 0x8 0x0 0x0 0x3 0x0;
interrupt-parent = mpc5200_pic;
gpio-controller;
#gpio-cells = 4;
};

There's no existing API in the GPIO system to describe this case. You
have to decide if you want an interrupt to be able to wake the CPU up
from sleep mode. If you want the interrupt to do this, it will trigger
int 3 if the CPU is asleep, otherwise it triggers int 8. Should these
pins have two virqs? or should these two vectors be hidden from the
user of the interrupt?

-- 
Jon Smirl
[EMAIL PROTECTED]
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: demuxing irqs

2008-09-14 Thread Jon Smirl
janiSat Jul 26 22:58:46 2008 UTC

  Modified files:  
/php-src/ext/sqlite3sqlite3.c 
  Log:
  fix folding tag
  
http://cvs.php.net/viewvc.cgi/php-src/ext/sqlite3/sqlite3.c?r1=1.3r2=1.4diff_format=u
Index: php-src/ext/sqlite3/sqlite3.c
diff -u php-src/ext/sqlite3/sqlite3.c:1.3 php-src/ext/sqlite3/sqlite3.c:1.4
--- php-src/ext/sqlite3/sqlite3.c:1.3   Sat Jul 26 22:39:56 2008
+++ php-src/ext/sqlite3/sqlite3.c   Sat Jul 26 22:58:45 2008
@@ -16,7 +16,7 @@
+--+
 */
 
-/* $Id: sqlite3.c,v 1.3 2008/07/26 22:39:56 jani Exp $ */
+/* $Id: sqlite3.c,v 1.4 2008/07/26 22:58:45 jani Exp $ */
 
 #ifdef HAVE_CONFIG_H
 #in

 












demuxing irqs
Jon Smirl


Re: demuxing irqs
Roland Dreier


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Roland Dreier


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Jon Smirl



Re: demuxing irqs
Jon Smirl
 

















 






  
  





Reply via email to



  
  





 
 








 












demuxing irqs
Jon Smirl


Re: demuxing irqs
Roland Dreier


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Roland Dreier


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Jon Smirl



Re: demuxing irqs
Jon Smirl
 

Re: demuxing irqs
Anton Vorontsov

Re: demuxing irqs
Jon Smirl



















 






  
  





Reply via email to



  
  





 
 








 












demuxing irqs
Jon Smirl


Re: demuxing irqs
Roland Dreier


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Roland Dreier


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Jon Smirl


Re: demuxing irqs
Jon Smirl



Re: demuxing irqs
Jon Smirl
 

Re: demuxing irqs
Anton Vorontsov

Re: demuxing irqs
Jon Smirl

Re: demuxing irqs
Anton Vorontsov

Re: demuxing irqs
Jon Smirl

Re: demuxing irqs
Anton Vorontsov

Re: demuxing irqs
Jon Smirl

Re: demuxing irqs
Scott Wood

Re: demuxing irqs
Jon Smirl

Re: demuxing irqs
Anton Vorontsov

Re: demuxing irqs
Jon Smirl



























 






  
  





Reply via email to