Menu
▾
▴
sdio-linux-devel — mail list for SDIO users and developers
You can subscribe to this list here.
| 2007 |
Jan
(3) |
Feb
(2) |
Mar
(6) |
Apr
(11) |
May
(4) |
Jun
(20) |
Jul
(13) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Nicolas P. <ni...@ca...> - 2007-06-12 16:48:20
|
On Tue, 12 Jun 2007, Ragner Magalhães wrote: > Hi, > On 6/12/07, Nicolas Pitre <ni...@ca...> wrote: > > > > I'm currently working closely with Pierre Ossman to add SDIO support > > into mainline. Because of the issues you noted above, the mainline SDIO > > support will probably be a complete rewrite. This is why I'm currently > > directing my current efforts towards this rewrite for the latest > > mainstream kernel instead of bringing the sdio-linux codebase forward. > > > Does MMC/SD/SDIO subsystem has a discussion mailing list ? The MMC/SD discussions typically happened on lin...@vg.... Since SDIO is just lifting up, discussions about the current stuff happened between Pierre and myself directly. I suspect that things will move to lkml when things start to get interesting, unless Pierre can be convinced to set up a dedicated list. Nicolas |
|
From: <ra...@us...> - 2007-06-12 16:22:33
|
Hi,
On 6/12/07, Nicolas Pitre <ni...@ca...> wrote:
>
> I'm currently working closely with Pierre Ossman to add SDIO support
> into mainline. Because of the issues you noted above, the mainline SDIO
> support will probably be a complete rewrite. This is why I'm currently
> directing my current efforts towards this rewrite for the latest
> mainstream kernel instead of bringing the sdio-linux codebase forward.
>
Does MMC/SD/SDIO subsystem has a discussion mailing list ?
Best regards,
--=20
Ragner N Magalh=E3es
Instituto Nokia de Tecnologia - INdT
Open Source Mobile Research Center - OSMRC
Linux Kernel Team
E-mail: rag...@in...
ra...@us...
|
|
From: Nicolas P. <ni...@ca...> - 2007-06-12 15:40:31
|
On Tue, 12 Jun 2007, Werner Almesberger wrote: > Hi all, > > I'm in the process of adding drivers for the Samsung 2410 and 2440 > MCUs for the OpenMoko project. We're tracking the latest mainstream > kernel, currently we're at 2.6.21.3. > > For now, I went back to an older kernel for sdio-linux, but I > wonder if you are already working on patches for more recent > kernels. If not, I'll look into this when done with the drivers. > > I'm also curious about plans for merging sdio-linux into the > mainstream kernel. I see mainly two areas where there could be > issues: 1) functionality overlaps with the existing SD/MMC > driver, and 2) the coding style is quite different from what's > required for mainline. Any thoughts on this ? I'm currently working closely with Pierre Ossman to add SDIO support into mainline. Because of the issues you noted above, the mainline SDIO support will probably be a complete rewrite. This is why I'm currently directing my current efforts towards this rewrite for the latest mainstream kernel instead of bringing the sdio-linux codebase forward. While the sdio-linux code base has its value as an already functional SDIO stack, it has some structural and major style issues that makes it impossible to ever be considered for mainline. There is another SDIO stack contender from Marvell that was turned down as well for the same reasons. Therefore I may only use this code as a working reference at this point. Because of that, if you're targeting the latest mainline kernel, I strongly suggest that you consider writing a host driver for the existing MMC/SD stack in mainline. The current SDIO effort is based on that. Pierre already pushed some of our SDIO work in his GIT tree at git://git2.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git. This is still early WIP but things are moving rather fast. Nicolas |
|
From: Paul L. <pl...@at...> - 2007-06-12 15:13:07
|
MontaVista is working on various kernel versions. They may be able to=20 give some additional insight. They are also working on supporting a=20 merged version. I do not have any details on it. Regards Paul -----Original Message----- From: Werner Almesberger [mailto:we...@op...]=20 Sent: Tuesday, June 12, 2007 3:09 AM To: sdi...@li... Subject: [Sdio-linux-devel] sdio-linux and recent kernels Hi all, I'm in the process of adding drivers for the Samsung 2410 and 2440 MCUs=20 for the OpenMoko project. We're tracking the latest mainstream kernel,=20 currently we're at 2.6.21.3. For now, I went back to an older kernel for sdio-linux, but I wonder if=20 you are already working on patches for more recent kernels. If not, I'll=20 look into this when done with the drivers. I'm also curious about plans for merging sdio-linux into the mainstream=20 kernel. I see mainly two areas where there could be issues: 1) functionality overlaps with the existing SD/MMC driver, and=20 2) the coding style is quite different from what's required for=20 mainline. Any thoughts on this ? - Werner -- =20 ________________________________________________________________________ _ / Werner Almesberger, Buenos Aires, Argentina =20 we...@al... / /_http://www.almesberger.net/___________________________________________ _/ ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C -=20 the FREE version of DB2 express and take control of your XML. No limits.=20 Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Sdio-linux-devel mailing list Sdi...@li... https://lists.sourceforge.net/lists/listinfo/sdio-linux-devel |
|
From: Paul L. <pl...@at...> - 2007-06-12 15:08:47
|
The HCD must not indicate that it supports SG DMA if it does not. This
would be a fatal error.
=20
Are you using a formatted SD memory card for this test? Try one with a
small size for testing say <1GB
=20
Paul
_____ =20
From: boku [mailto:bok...@gm...]=20
Sent: Tuesday, June 12, 2007 2:40 AM
To: sdi...@li...
Subject: Re: [Sdio-linux-devel] Kernel panic for sd memory
I've checked my SDHC driver and found it doesn't support DMA but report
it can support.=20
=20
This comes out a thought that if no DMA is support by SDHC, the
pReq->pDataBuffer is simply as a data buffer pointer=20
instead of being a pointer to the SGlist data structure. Is it? I think
that's the problem. Sorry about this confusion.=20
=20
However, I met another problem while keep going on.=20
=3D> While I try to mount the sd memory device, it complains:
/dev/sdio0p1 is not a valid block device
=20
I followed the steps shown in the sdio-linux reference document. Below
are some info I did.=20
=20
=20
-sh-2.05b# ls -l /dev/sdio*
brw-r--r-- 1 root root 254, 1 Jun 8 2007 /dev/sdio0p1
-sh-2.05b# cat /proc/devices=20
Character devices:
1 mem
2 pty
3 ttyp
4 /dev/vc/0
4 tty
5 /dev/tty
5 /dev/console
5 /dev/ptmx
7 vcs
10 misc
13 input=20
21 sg
29 fb
81 video4linux
86 ch
90 mtd
128 ptm
136 pts
204 ttyAM
204 ttyAMA
Block devices:
1 ramdisk
7 loop
31 mtdblock
254 sdmem
=20
-sh-2.05b# mount -t vfat /dev/sdio0p1 /mnt/sdmem/
+SDIO Memory Function: Open
-SDIO Memory Function: Open
+SDIO Memory Function: Release(INST=3D0xc7263c00)
-SDIO Memory Function: Release
mount: /dev/sdio0p1 is not a valid block device
=20
=20
The message of insert module is as follows:=20
=2E......
SDIO Memory Function: Probe - creating disk=20
+SDIO Memory Function: CreateDisk
SDIO Memory Function: blk_init_Q using DiskRequest
SDIO Memory Function: block size 512
SDIO Memory Function: setting block size 512=20
SDIO Memory Function: CreateDisk: size 1983488 (Size 992000,
FileSysBlockSize 512)
+SDIO Memory Function: Open
-SDIO Memory Function: Open
SDIO Memory Function: ReadBlocks reading, count/size length 8/512 4096
cmd: 18=20
SDIO MUSTANG HOST SetUpHCDDMA (RX) Blocks:8, BlockLen:512
SDIO MUSTANG HOST HcdRequest RX Data Transfer, Blocks:8, BlockLen:512=20
HcdRequest - RespType:1, Flgs=3D0x00004201, Command:18 , Arg:0x0,
txMode=3D0x00000014
SDIO Bus Driver: HCD returned status:3 on request: 0xC7295F00,
(CMD:18)(Flags:00004201)=20
HcdSDInterrupt, ints: 0x281F errors: 0x0, sigenables: 0x2000,
statenable: 0x733F errorenables:0x7F7F
GetResp=3D00000012 00000900=20
HcdSDInterrupt - RX Data Transfer Complete with status:0
-HcdSDInterrupt
SDIO Bus Driver: Sync-Op signal waiting....
SDIO Bus Driver: SDIO_HandleHcdEvent, event type 0x4, HCD:0xBF0178D8
SDIO Bus Driver: _SDIO_HandleHcdEvent, event type 0x4, HCD:0xBF0178D8=20
+SDIO Bus Driver: Handling Transfer Done (CMD:18, Status:0,
Flags=3D00004201, Req=3D0xc7295f00) from HCD:0xBF0178D8=20
SDIO Bus Driver: Queue idle=20
SDIO Bus Driver: Calling completion on request:0xC7295F00, CMD:18=20
-SDIO Bus Driver: Transfer Done Handled=20
-SDIO Memory Function: DiskRequest
+SDIO Memory Function: Release(INST=3D0xc7245c00)
-SDIO Memory Function: Release
-SDIO Memory Function: CreateDisk major: 254, minors: 8, first_minor: 0=20
-SDIO Memory Function: CreateDisk
=20
|
|
From: Werner A. <we...@op...> - 2007-06-12 10:09:03
|
Hi all, I'm in the process of adding drivers for the Samsung 2410 and 2440 MCUs for the OpenMoko project. We're tracking the latest mainstream kernel, currently we're at 2.6.21.3. For now, I went back to an older kernel for sdio-linux, but I wonder if you are already working on patches for more recent kernels. If not, I'll look into this when done with the drivers. I'm also curious about plans for merging sdio-linux into the mainstream kernel. I see mainly two areas where there could be issues: 1) functionality overlaps with the existing SD/MMC driver, and 2) the coding style is quite different from what's required for mainline. Any thoughts on this ? - Werner -- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina we...@al... / /_http://www.almesberger.net/____________________________________________/ |
|
From: boku <bok...@gm...> - 2007-06-12 09:40:04
|
I've checked my SDHC driver and found it doesn't support DMA but report it
can support.
This comes out a thought that if no DMA is support by SDHC, the
pReq->pDataBuffer is simply as a data buffer pointer
instead of being a pointer to the SGlist data structure. Is it? I think
that's the problem. Sorry about this confusion.
However, I met another problem while keep going on.
=> While I try to mount the sd memory device, it complains:
/dev/sdio0p1 is not a valid block device
I followed the steps shown in the sdio-linux reference document. Below are
some info I did.
*-sh-2.05b# ls -l /dev/sdio*
*brw-r--r-- 1 root root 254, 1 Jun 8 2007 /dev/sdio0p1
*-sh-2.05b# cat /proc/devices
*Character devices:
1 mem
2 pty
3 ttyp
4 /dev/vc/0
4 tty
5 /dev/tty
5 /dev/console
5 /dev/ptmx
7 vcs
10 misc
13 input
21 sg
29 fb
81 video4linux
86 ch
90 mtd
128 ptm
136 pts
204 ttyAM
204 ttyAMA
Block devices:
1 ramdisk
7 loop
31 mtdblock
254 sdmem
*-sh-2.05b# mount -t vfat /dev/sdio0p1 /mnt/sdmem/
*+SDIO Memory Function: Open
-SDIO Memory Function: Open
+SDIO Memory Function: Release(INST=0xc7263c00)
-SDIO Memory Function: Release
*mount: /dev/sdio0p1 is not a valid block device
*
The message of insert module is as follows:
.......
SDIO Memory Function: Probe - creating disk
+SDIO Memory Function: CreateDisk
SDIO Memory Function: blk_init_Q using DiskRequest
SDIO Memory Function: block size 512
SDIO Memory Function: setting block size 512
SDIO Memory Function: CreateDisk: size 1983488 (Size 992000,
FileSysBlockSize 512)
+SDIO Memory Function: Open
-SDIO Memory Function: Open
SDIO Memory Function: ReadBlocks reading, count/size length 8/512 4096 cmd:
18
SDIO MUSTANG HOST SetUpHCDDMA (RX) Blocks:8, BlockLen:512
SDIO MUSTANG HOST HcdRequest RX Data Transfer, Blocks:8, BlockLen:512
HcdRequest - RespType:1, Flgs=0x00004201, Command:18 , Arg:0x0,
txMode=0x00000014
SDIO Bus Driver: HCD returned status:3 on request: 0xC7295F00,
(CMD:18)(Flags:00004201)
HcdSDInterrupt, ints: 0x281F errors: 0x0, sigenables: 0x2000, statenable:
0x733F errorenables:0x7F7F
GetResp=00000012 00000900
HcdSDInterrupt - RX Data Transfer Complete with status:0
-HcdSDInterrupt
SDIO Bus Driver: Sync-Op signal waiting....
SDIO Bus Driver: SDIO_HandleHcdEvent, event type 0x4, HCD:0xBF0178D8
SDIO Bus Driver: _SDIO_HandleHcdEvent, event type 0x4, HCD:0xBF0178D8
+SDIO Bus Driver: Handling Transfer Done (CMD:18, Status:0, Flags=00004201,
Req=0xc7295f00) from HCD:0xBF0178D8
SDIO Bus Driver: Queue idle
SDIO Bus Driver: Calling completion on request:0xC7295F00, CMD:18
-SDIO Bus Driver: Transfer Done Handled
-SDIO Memory Function: DiskRequest
+SDIO Memory Function: Release(INST=0xc7245c00)
-SDIO Memory Function: Release
-SDIO Memory Function: CreateDisk major: 254, minors: 8, first_minor: 0
-SDIO Memory Function: CreateDisk
|
|
From: boku <bok...@gm...> - 2007-06-12 02:22:28
|
Hi,
I'm writing my platform's SDHC and testing the sd memory function.
However, there's a kernel panic while creating disk. My environment is
ARM-based platform on Linux kernel 2.6.15. Therefore, I modified a few code
for porting to 2.6.15 since the patch is based on 2.6.18. The message is
pasted as follows. I noticed there is a call to sdmem's Release function. Is
it the cause of the panic? Thanks!~
.........
SDIO Memory Function: Probe - creating disk
+SDIO Memory Function: CreateDisk
SDIO Memory Function: blk_init_Q using DiskRequestDma(0x00000001)
SDIO Memory Function: block size 512
SDIO Memory Function: setting block size 512
SDIO Memory Function: setting up DMA
SDIO Memory Function: CreateDisk: size 1983488 (Size 992000,
FileSysBlockSize 512)
+SDIO Memory Function: Open
-SDIO Memory Function: Open
SDIO Memory Function: DiskRequestDma : processing block request :0xC7E53084
SDIO Memory Function: DiskRequestDma - Phys Segments 1, HW Segments:1,
current_nr_sectors:8, nr_sectors:8 , hard_nr_sectors:8
SDIO Memory Function: DiskRequestDma - SG entries: 1, sector start: 0,
seccnt: 8
SDIO Memory Function: DiskRequestDma - SG Index:0, page: 0xC0399A20, length:
4096, offset: 0x0
SDIO Memory Function: DiskRequestDma - submitting Read using SG entries:
1,len: 4096
SDIO Memory Function: SGcnt>0, DATA_DMA
SDIO Memory Function: IssueAsyncTransfer (RX), (count/blksize:8/512)
(length:4096) cmd: 18
SDIO MUSTANG HOST SetUpHCDDMA (RX) Blocks:8, BlockLen:512
SDIO MUSTANG HOST HcdRequest RX Data Transfer, Blocks:8, BlockLen:512
HcdRequest - RespType:1, Flgs=0x00005211, Command:18 , Arg:0x0,
txMode=0x00000014
SDIO Bus Driver: HCD returned status:3 on request: 0xC729DCC0,
(CMD:18)(Flags:00005211)
HcdSDInterrupt, ints: 0x281F errors: 0x0, sigenables: 0x2000, statenable:
0x733F errorenables:0x7F7F
GetResp=00000012 00000900
HcdSDInterrupt - RX Data Transfer Complete with status:0
-HcdSDInterrupt
-SDIO Memory Function: DiskRequestDma
SDIO Bus Driver: SDIO_HandleHcdEvent, event type 0x4, HCD:0xBF017954
SDIO Bus Driver: _SDIO_HandleHcdEvent, event type 0x4, HCD:0xBF017954
+SDIO Bus Driver: Handling Transfer Done (CMD:18, Status:0, Flags=00005211,
Req=0xc729dcc0) from HCD:0xBF017954
SDIO Bus Driver: Queue idle
SDIO Bus Driver: Calling completion on request:0xC729DCC0, CMD:18
+SDIO Memory Function: AsyncCompletionLast: status: 0, (0xC7251000)
SDIO Memory Function: completed sectors :8 nr_sectors: 8, Status=0
SDIO Memory Function: current disk request done!(0xc7e53084)
+SDIO Memory Function: DiskRequestDma
-SDIO Memory Function: DiskRequestDma
-SDIO Memory Function: AsyncCompletionLast
-SDIO Bus Driver: Transfer Done Handled
+SDIO Memory Function: Release(INST=0xc724ec00)
-SDIO Memory Function: Release
-SDIO Memory Function: CreateDisk major: 254, minors: 8, first_minor: 0
-SDIO Memory Function: CreateDisk
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c0004000
[00000000] *pgd=00000000
Internal error: Oops: 817 [#1]
Modules linked in: sdio_memory_fd sdio_mustanghcd sdio_busdriver sdio_lib
CPU: 0
PC is at free_block+0x54/0x124
LR is at drain_array_locked+0x90/0xb8
pc : [<c00676d8>] lr : [<c0067838>] Not tainted
sp : c7c31ef8 ip : c7aab800 fp : c7c31f20
r10: 00000000 r9 : c03fd230 r8 : 00000005
r7 : 00000000 r6 : c02b46c0 r5 : c03fe4a0 r4 : c7599aa0
r3 : 00000000 r2 : 00000000 r1 : c03fd230 r0 : c02b46c0
Flags: Nzcv IRQs off FIQs on Mode SVC_32 Segment kernel
Control: 5717F Table: 07B08000 DAC: 00000017
Process events/0 (pid: 4, stack limit = 0xc7c30194)
Stack: (0xc7c31ef8 to 0xc7c32000)
1ee0: 00000005
c03fd220
1f00: c03fd230 00000016 c029d890 00000000 c029d8a0 c7c31f40 c7c31f24
c0067838
1f20: c0067694 c03fe4a0 00000000 c02b46c0 c02b470c c7c31f6c c7c31f44
c0068808
1f40: c00677b8 c7c036f0 80000013 c7c036e8 c0068770 c7c31f88 c7c036e0
fffffffc
1f60: c7c31fc0 c7c31f70 c0051de0 c0068780 ffffffff ffffffff 00000001
00000000
1f80: c003e9c8 00010000 00000000 00000000 c7c0e540 c003e9c8 00100100
00200200
1fa0: c7c036e0 c7c30000 c0051c18 c7c17f24 00000001 c7c31ff4 c7c31fc4
c00564c4
1fc0: c0051c28 00000001 ffffffff ffffffff 00000000 00000000 00000000
00000000
1fe0: 00000000 00000000 00000000 c7c31ff8 c0043c4c c00563ec a5a2c5a7
585adadb
Backtrace:
|
|
From: Paul L. <pl...@at...> - 2007-06-06 16:28:34
|
There is a discussion of hardware on the source forge site. Look on the front page of http://sourceforge.net/projects/sdio-linux/ =20 Paul _____ =20 From: boku [mailto:bok...@gm...]=20 Sent: Tuesday, June 05, 2007 11:37 PM To: sdi...@li... Subject: [Sdio-linux-devel] Any SDIO functional card suggestion? Hi, So far, could you suggest those products which have been tested successfully by this project on GPS, Bluetooth or other devices?=20 I'd like to verify our platform with various functional devices. Thank you!=20 =20 Best Regards, Boku =20 |
|
From: boku <bok...@gm...> - 2007-06-06 06:37:27
|
Hi,
So far, could you suggest those products which have been tested
successfully by this project on GPS, Bluetooth or other devices?
I'd like to verify our platform with various functional devices. Thank you!
Best Regards,
Boku
|
|
From: Paul L. <pl...@at...> - 2007-05-16 16:07:22
|
The AR6001 WLAN chip is used in a number of mobile devices. It is
typically used in a module package and mounted on the devices main PCB.
The module is usually communicated with via SDIO. The AR6K is not
available as an after market plug in SDIO card, except for the
CardAccess Dev kit as far as I know.
=20
Regards
=20
Paul
_____ =20
From: boku [mailto:bok...@gm...]=20
Sent: Wednesday, May 16, 2007 12:27 AM
To: sdi...@li...
Subject: [Sdio-linux-devel] questions about the WLAN product?
Hi,=20
I'd like to ask besides the CardAcccess's WLAN card, are there any
other WLAN SDIO I can use as my function driver?
Is there any other card using Atheros' AR6000? If there exists, I
can use it on this project, right?=20
Thanks!~
=20
Best Regards,
=20
|
|
From: boku <bok...@gm...> - 2007-05-16 07:27:33
|
Hi,
I'd like to ask besides the CardAcccess's WLAN card, are there any
other WLAN SDIO I can use as my function driver?
Is there any other card using Atheros' AR6000? If there exists, I can
use it on this project, right?
Thanks!~
Best Regards,
|
|
From: Paul L. <pl...@at...> - 2007-05-03 16:17:00
|
What file has the DBG_PRINT message in the source tree?
The flag does mean that command has data associated with it. Most host
controller drivers make decisions on whether to complete a command
inline or via an interrupt based on the how long the command should take
to complete across the bus, how long a spin wait should be allowed, etc.
This reduces the interrupt rate and significantly improves throughput.
=20
Regards
=20
Paul
_____ =20
From: boku [mailto:bok...@gm...]=20
Sent: Wednesday, May 02, 2007 9:36 PM
To: Nicolas Pitre; sdi...@li...
Subject: [Sdio-linux-devel] pReq->Flags & SDREQ_FLAGS_DATA_TRANS??
Hi,=20
In the following code, is it reversed for the determination of
"command only" or "with data"?=20
the SDREQ_FLAGS_DATA_TRANS means the transfer is with data, isn't it?=20
Thank you!=20
DBG_PRINT(MUSTANG_HOST_TRACE_REQUESTS, ("SDIO MUSTANG HOST
HcdRequest using interrupt for command done (%s). (clock:%d, ref:%d)\n",
(pReq->Flags & SDREQ_FLAGS_DATA_TRANS ) ? "command only" : "with data",
SDHCD_GET_OPER_CLOCK(pHcd), pHcInstance->ClockSpinLimit));
=20
|
|
From: boku <bok...@gm...> - 2007-05-03 04:36:19
|
Hi,
In the following code, is it reversed for the determination of "command
only" or "with data"?
the SDREQ_FLAGS_DATA_TRANS means the transfer is with data, isn't it?
Thank you!
DBG_PRINT(MUSTANG_HOST_TRACE_REQUESTS, ("SDIO MUSTANG HOST
HcdRequest using interrupt for command done (%s). (clock:%d,
ref:%d)\n", (pReq->Flags & SDREQ_FLAGS_DATA_TRANS) ?
"command only" : "with data", SDHCD_GET_OPER_CLOCK(pHcd),
pHcInstance->ClockSpinLimit));
|
|
From: Paul L. <pl...@at...> - 2007-04-25 16:01:42
|
Boku,
The USE_CARD_DETECT_HW assumes that there is a micro-switch attached to
a GPIO line that detects card insert or removal. The default method for
detecting insert/removal is set to SDHCD_ATTRIB_SLOT_POLLING in the
PXA270 HCD. In this case, a periodic innocuous command is sent down to
the slot to determine if the a card is present.
=20
Regards
=20
Paul
_____ =20
From: boku [mailto:bok...@gm...]=20
Sent: Wednesday, April 25, 2007 2:19 AM
To: sdi...@li...
Subject: [Sdio-linux-devel] #ifdef USE_CARD_DETECT_HW in HCD driver?
Hi,=20
I'm doing the host controller driver now. There is such define check
in HCD driver. What's it used for? I check PXA270/ and found it doesn't
define such variable. Therefore, how to detect the card
insertion/removal in PXA270? Thanks~=20
=20
Best Regards,
boku
=20
|
|
From: Paul L. <pl...@at...> - 2007-04-25 14:20:15
|
The Standard Host Spec is available at=20 http://www.sdcard.org/HostController/index.html =20 Paul _____ =20 From: boku [mailto:bok...@gm...]=20 Sent: Wednesday, April 25, 2007 3:59 AM To: sdi...@li... Subject: [Sdio-linux-devel] stdhost? Is there any spec for stdhost?=20 It seems to be compiled into pci_std/?=20 Thanks!~ =20 |
|
From: boku <bok...@gm...> - 2007-04-25 10:59:07
|
Is there any spec for stdhost? It seems to be compiled into pci_std/? Thanks!~ |
|
From: boku <bok...@gm...> - 2007-04-25 09:18:49
|
Hi,
I'm doing the host controller driver now. There is such define check in
HCD driver. What's it used for? I check PXA270/ and found it doesn't define
such variable. Therefore, how to detect the card insertion/removal in
PXA270? Thanks~
Best Regards,
boku
|
|
From: Nicolas P. <ni...@ca...> - 2007-04-20 14:40:54
|
On Fri, 20 Apr 2007, boku wrote:
> Hi,
> I'm using 2.6.18 and patching the sdio source code. My target is PXA270.
> But when I attempt make kernel, it shows errors at compiling the pnp as
> follows:
> drivers/built-in.o: In function `pnp_check_dma':
> drivers/pnp/resource.c:453: undefined reference to `request_dma'
> drivers/pnp/resource.c:455: undefined reference to `free_dma'
>
> Do I need to select the pnp if I wanna have a p&p sdio device no matter it's
> memory device or sdio device?
For now the code requires CONFIG_PNP to be active. That will change
eventually.
In the mean time, please try this patch on top of the others:
Index: linux/drivers/pnp/resource.c
===================================================================
--- linux.orig/drivers/pnp/resource.c
+++ linux/drivers/pnp/resource.c
@@ -420,7 +420,7 @@ int pnp_check_irq(struct pnp_dev * dev,
int pnp_check_dma(struct pnp_dev * dev, int idx)
{
-#ifndef CONFIG_IA64
+#if !defined(CONFIG_IA64) && !defined(CONFIG_ARM)
int tmp;
struct pnp_dev *tdev;
resource_size_t * dma = &dev->res.dma_resource[idx].start;
Nicolas
|
|
From: boku <bok...@gm...> - 2007-04-20 08:28:49
|
Hi,
I'm using 2.6.18 and patching the sdio source code. My target is PXA270.
But when I attempt make kernel, it shows errors at compiling the pnp as
follows:
drivers/built-in.o: In function `pnp_check_dma':
drivers/pnp/resource.c:453: undefined reference to `request_dma'
drivers/pnp/resource.c:455: undefined reference to `free_dma'
Do I need to select the pnp if I wanna have a p&p sdio device no matter it's
memory device or sdio device?
Thanks!~
Regards,
boku
|
|
From: Sandhya S. <san...@pa...> - 2007-04-16 04:43:40
|
I have following three queries. 1) I am using Ellen 2 Board on 2.6.18. When I applied the SDIO patch and did the "make menuconfig" the PCIELLEN HCD has been automatically configured as MODULE. But when I walked through the code I found that the PCISTD HCD supports Ellen 1 & Ellen 2, but PCLELLEN HCD is for Ellen 1. Will the PCLELLEN Hcd can work with Ellen 2 Board? 2) With the above setup, I had checked with SanDisk SD Card after loading the following modules sdio_lib sdio_busdriver sdio_pciellen_hcd When I inserted the card the usage count of sdio_pciellen_hcd has increased from 0 to 1. But when I removed the card the usage count didn't decrement. Is this observation OK or it is abnormal result? 3) Can the SanDisk SD card work with the sample memory function driver comes along with the SDIO subsystem? Regards Sandhya |
|
From: Shanmugasundaram A. <ass...@gm...> - 2007-04-16 01:23:27
|
Hi, I have threequeries. 1) I am using Ellen 2 Board on 2.6.18. When I applied the SDIO patch and did the "make menuconfig" the PCIELLEN HCD has been automattically configured as MODULE. But when I walked through the code I found that the PCISTD HCD supports Ellen 1 & Ellen 2, but PCLELLEN HCD is for Ellen 1. Will the PCLELLEN Hcd can work with Ellen 2 Board? 2) With the above setup, I had checked with SanDisk SD Card after loading the following modules sdio_lib sdio_busdriver sdio_pciellen_hcd When I inserted the card the usage count of sdio_pciellen_hcd has increased from 0 to 1. But when I removed the card the usage count didn't decrement. Is this observation OK or it is abnormal result? 3) Can the SanDisk SD card work with the sample memory function driver comes along with the SDIO subsytem? Regards, Sundar |
|
From: Shanmugasundaram A. <ass...@gm...> - 2007-04-16 01:20:04
|
Hi, I have three queries. 1) I am using Ellen 2 Board on 2.6.18. When I applied the SDIO patch and did the "make menuconfig" the PCIELLEN HCD has been automattically configured as MODULE. But when I walked through the code I found that the PCISTD HCD supports Ellen 1 & Ellen 2, but PCLELLEN HCD is for Ellen 1. Will the PCLELLEN Hcd can work with Ellen 2 Board? 2) With the above setup, I had checked with SanDisk SD Card after loading the following modules sdio_lib sdio_busdriver sdio_pciellen_hcd When I inserted the card the usage count of sdio_pciellen_hcd has increased from 0 to 1. But when I removed the card the usage count didn't decrement. Is this observation OK or it is abnormal result? 3) Can the SanDisk SD card work with the sample memory function driver comes along with the SDIO subsytem? Regards, Sundar |
|
From: Paul L. <pl...@at...> - 2007-04-09 01:20:41
|
There are many implementations that use the AR6001. Most of these are=20 SDIO and are embedded in mobile devices. The bulk of the driver is=20 specific to the AR6K chipset. The upper portions of the driver handle=20 the generic network interface for a WLAN device and could be re-used. Paul -----Original Message----- From: Michel Stempin [mailto:mic...@wa...]=20 Sent: Sunday, April 08, 2007 11:13 AM To: sdi...@li... Subject: [Sdio-linux-devel] Supported commarcial SDIO WLAN cards Hi list, Is there any existing/expected commercial SDIO WLAN card product for the=20 Atheros AR6001 chipset, beside the CardAccess evaluation card? Also, how much of the driver is applicable to a different chipset? Is it=20 completely dependant on the AR6001 chipset or can part of the driver be=20 re-used for another chipset? Regards, -- Michel Stempin ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share=20 your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV _______________________________________________ Sdio-linux-devel mailing list Sdi...@li... https://lists.sourceforge.net/lists/listinfo/sdio-linux-devel |
|
From: Michel S. <mic...@wa...> - 2007-04-08 18:13:34
|
Hi list, Is there any existing/expected commercial SDIO WLAN card product for the Atheros AR6001 chipset, beside the CardAccess evaluation card? Also, how much of the driver is applicable to a different chipset? Is it completely dependant on the AR6001 chipset or can part of the driver be re-used for another chipset? Regards, -- Michel Stempin |
1 message has been excluded from this view by a project administrator.
