(no subject)

(no subject)

[Niyanth, Venkata]

Hi,
     I am working on OMAP5912, i am planning to develop some multimedia applications.
Presently i am working on linux platform and planning to port Windows mobile on the board.
Is it possible to have windows mobile on the board ?
 

Re: (no subject)

[Tony Lindgren]

* Niyanth, Venkata <VNiyanth@ciber.com> [061219 01:27]:
> Hi,
>      I am working on OMAP5912, i am planning to develop some multimedia applications.
> Presently i am working on linux platform and planning to port Windows mobile on the board.
> Is it possible to have windows mobile on the board ?

This is a Linux mailing list, it's unlikely that you find an answer here.

Tony

(no subject)

[Tony Lindgren]

As the musb/tusb code now mostly works for host and peripheral,
I'm planning to push a series of search and replace patches
to start converting the musb/tusb driver into something that
follows CodingStyle.

Following is a list of changes I've done. I haven't gone through
DaVinci or 2430 specific code, as I cannot test them right now.
No functional changes should be included. Code has been tested
with tusb6010.

Regards,

Tony

[PATCH 1/52] musb_hdrc: Search and replace pThis with musb
[PATCH 2/52] musb_hdrc: Search and replace pEndPt with hw_ep
[PATCH 3/52] musb_hdrc: Search and replace pEnd with musb_ep when struct musb_ep
[PATCH 4/52] musb_hdrc: Search and replace pEnd with musb_ep when struct musb_hw_ep
[PATCH 5/52] musb_hdrc: Search and replace pRegs with mregs
[PATCH 6/52] musb_hdrc: Search and replace pBase with mbase
[PATCH 7/52] musb_hdrc: Search and replace pSource with src
[PATCH 8/52] musb_hdrc: Search and replace pDest with dst
[PATCH 9/52] musb_hdrc: Search and replace dwCount with len
[PATCH 10/52] musb_hdrc: Search and replace wFifoCount with fifo_count
[PATCH 11/52] musb_hdrc: Search and replace wCount with len
[PATCH 12/52] musb_hdrc: Search and replace bLocalEnd with epnum
[PATCH 13/52] musb_hdrc: Search and replace aLocalEnd with endpoints
[PATCH 14/52] musb_hdrc: Search and replace bEndCount with nr_endpoints
[PATCH 15/52] musb_hdrc: Search and replace bEndNumber with current_epnum
[PATCH 16/52] musb_hdrc: Search and replace bEnd0Stage with ep0_stage
[PATCH 17/52] musb_hdrc: Search and replace bEnd with epnum
[PATCH 18/52] musb_hdrc: Search and replace Lock with lock
[PATCH 19/52] musb_hdrc: Search and replace MGC_SelectEnd with musb_ep_select
[PATCH 20/52] musb_hdrc: Search and replace _pthis with _musb
[PATCH 21/52] musb_hdrc: Search and replace bIsHost with is_host
[PATCH 22/52] musb_hdrc: Get rid of old unused MUSB_EpFifoDescriptor
[PATCH 23/52] musb_hdrc: Search and replace bIsSharedFifo with is_shared_fifo
[PATCH 24/52] musb_hdrc: Search and replace wMaxPacketSizeTx with max_packet_sz_tx
[PATCH 25/52] musb_hdrc: Search and replace wMaxPacketSizeRx with max_packet_sz_rx
[PATCH 26/52] musb_hdrc: Search and replace pDmaController with dma_controller
[PATCH 27/52] musb_hdrc: Search and replace bIsMultipoint with is_multipoint
[PATCH 28/52] musb_hdrc: Search and replace bIgnoreDisconnect with ignore_disconnect
[PATCH 29/52] musb_hdrc: Search and replace bBulkSplit with bulk_split
[PATCH 30/52] musb_hdrc: Search and replace bBulkCombine with bulk_combine
[PATCH 31/52] musb_hdrc: Search and replace bAddress with address
[PATCH 32/52] musb_hdrc: Search and replace bTestModeValue with test_mode_nr
[PATCH 33/52] musb_hdrc: Search and replace bTestMode with test_mode
[PATCH 34/52] musb_hdrc: Search and replace pGadgetDriver with gadget_driver
[PATCH 35/52] musb_hdrc: Search and replace bDelayPortPowerOff with delay_port_power_off
[PATCH 36/52] musb_hdrc: Search and replace pProcEntry with proc_entry
[PATCH 37/52] musb_hdrc: Search and replace pPrivateData with private_data
[PATCH 38/52] musb_hdrc: Search and replace dwMaxLength with max_len
[PATCH 39/52] musb_hdrc: Search and replace dwActualLength with actual_len
[PATCH 40/52] musb_hdrc: Search and replace bStatus with status
[PATCH 41/52] musb_hdrc: Search and replace bDesiredMode with desired_mode
[PATCH 42/52] musb_hdrc: Search and replace bMode with mode
[PATCH 43/52] musb_hdrc: Search and replace MGC_pfDmaProgramChannel with dma_program_channel
[PATCH 44/52] musb_hdrc: Search and replace pControlRequest with ctrlrequest
[PATCH 45/52] musb_hdrc: Search and replace bResult with result
[PATCH 46/52] musb_hdrc: Search and replace bSetAddress with set_address
[PATCH 47/52] musb_hdrc: Search and replace bRecip with recip
[PATCH 48/52] musb_hdrc: Search and replace pRequest with request
[PATCH 49/52] musb_hdrc: Search and replace wCsrVal with csr
[PATCH 50/52] musb_hdrc: Search and replace bTx with tx
[PATCH 51/52] musb_hdrc: Search and replace wPacketSize with packet_sz
[PATCH 52/52] musb_hdrc: Search and replace channelNum with chnum

Re: (no subject)

[Felipe Balbi]

Hi Tony,

On 8/13/07, Tony Lindgren <tony@atomide.com> wrote:
> As the musb/tusb code now mostly works for host and peripheral,
> I'm planning to push a series of search and replace patches
> to start converting the musb/tusb driver into something that
> follows CodingStyle.
>
> Following is a list of changes I've done. I haven't gone through
> DaVinci or 2430 specific code, as I cannot test them right now.
> No functional changes should be included. Code has been tested
> with tusb6010.

Thanks a lot for your patch series... I was planning to do such
cleanup a while ago but got stuck on some activities and this has gone
to less priority queue.

Anyway, I'll try to get a time to test this patches and I'll report
you any trouble I find. :-)

>
> Regards,
>
> Tony
>
> [PATCH 1/52] musb_hdrc: Search and replace pThis with musb
> [PATCH 2/52] musb_hdrc: Search and replace pEndPt with hw_ep
> [PATCH 3/52] musb_hdrc: Search and replace pEnd with musb_ep when struct musb_ep
> [PATCH 4/52] musb_hdrc: Search and replace pEnd with musb_ep when struct musb_hw_ep
> [PATCH 5/52] musb_hdrc: Search and replace pRegs with mregs
> [PATCH 6/52] musb_hdrc: Search and replace pBase with mbase
> [PATCH 7/52] musb_hdrc: Search and replace pSource with src
> [PATCH 8/52] musb_hdrc: Search and replace pDest with dst
> [PATCH 9/52] musb_hdrc: Search and replace dwCount with len
> [PATCH 10/52] musb_hdrc: Search and replace wFifoCount with fifo_count
> [PATCH 11/52] musb_hdrc: Search and replace wCount with len
> [PATCH 12/52] musb_hdrc: Search and replace bLocalEnd with epnum
> [PATCH 13/52] musb_hdrc: Search and replace aLocalEnd with endpoints
> [PATCH 14/52] musb_hdrc: Search and replace bEndCount with nr_endpoints
> [PATCH 15/52] musb_hdrc: Search and replace bEndNumber with current_epnum
> [PATCH 16/52] musb_hdrc: Search and replace bEnd0Stage with ep0_stage
> [PATCH 17/52] musb_hdrc: Search and replace bEnd with epnum
> [PATCH 18/52] musb_hdrc: Search and replace Lock with lock
> [PATCH 19/52] musb_hdrc: Search and replace MGC_SelectEnd with musb_ep_select
> [PATCH 20/52] musb_hdrc: Search and replace _pthis with _musb
> [PATCH 21/52] musb_hdrc: Search and replace bIsHost with is_host
> [PATCH 22/52] musb_hdrc: Get rid of old unused MUSB_EpFifoDescriptor
> [PATCH 23/52] musb_hdrc: Search and replace bIsSharedFifo with is_shared_fifo
> [PATCH 24/52] musb_hdrc: Search and replace wMaxPacketSizeTx with max_packet_sz_tx
> [PATCH 25/52] musb_hdrc: Search and replace wMaxPacketSizeRx with max_packet_sz_rx
> [PATCH 26/52] musb_hdrc: Search and replace pDmaController with dma_controller
> [PATCH 27/52] musb_hdrc: Search and replace bIsMultipoint with is_multipoint
> [PATCH 28/52] musb_hdrc: Search and replace bIgnoreDisconnect with ignore_disconnect
> [PATCH 29/52] musb_hdrc: Search and replace bBulkSplit with bulk_split
> [PATCH 30/52] musb_hdrc: Search and replace bBulkCombine with bulk_combine
> [PATCH 31/52] musb_hdrc: Search and replace bAddress with address
> [PATCH 32/52] musb_hdrc: Search and replace bTestModeValue with test_mode_nr
> [PATCH 33/52] musb_hdrc: Search and replace bTestMode with test_mode
> [PATCH 34/52] musb_hdrc: Search and replace pGadgetDriver with gadget_driver
> [PATCH 35/52] musb_hdrc: Search and replace bDelayPortPowerOff with delay_port_power_off
> [PATCH 36/52] musb_hdrc: Search and replace pProcEntry with proc_entry
> [PATCH 37/52] musb_hdrc: Search and replace pPrivateData with private_data
> [PATCH 38/52] musb_hdrc: Search and replace dwMaxLength with max_len
> [PATCH 39/52] musb_hdrc: Search and replace dwActualLength with actual_len
> [PATCH 40/52] musb_hdrc: Search and replace bStatus with status
> [PATCH 41/52] musb_hdrc: Search and replace bDesiredMode with desired_mode
> [PATCH 42/52] musb_hdrc: Search and replace bMode with mode
> [PATCH 43/52] musb_hdrc: Search and replace MGC_pfDmaProgramChannel with dma_program_channel
> [PATCH 44/52] musb_hdrc: Search and replace pControlRequest with ctrlrequest
> [PATCH 45/52] musb_hdrc: Search and replace bResult with result
> [PATCH 46/52] musb_hdrc: Search and replace bSetAddress with set_address
> [PATCH 47/52] musb_hdrc: Search and replace bRecip with recip
> [PATCH 48/52] musb_hdrc: Search and replace pRequest with request
> [PATCH 49/52] musb_hdrc: Search and replace wCsrVal with csr
> [PATCH 50/52] musb_hdrc: Search and replace bTx with tx
> [PATCH 51/52] musb_hdrc: Search and replace wPacketSize with packet_sz
> [PATCH 52/52] musb_hdrc: Search and replace channelNum with chnum
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>


-- 
Best Regards,

Felipe Balbi
felipebalbi@users.sourceforge.net

(no subject)

[il]

-- 
Hello,
801,613 Euro is now yours. Congrats... You have won.

Send your information to Monte Fred +44-704-574-9850 on
barrkellymoore@9.cn to help you process your claims.
Provide your name, address, age, phone number, occupation.

(no subject)

[Cgnlwin]

Get back to us for a lump sum pay out of £891,934.00 GBP. Provide Your
Name:___ Address:___ Age:___ Sex:___ Occupation:___
Tel/Fax:___Country.Email claims.max@gala.net )TEL (+4470359 60749 )for
claims immediately.

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

(no subject)

[Camelot Uk]

Participate in our Uk monthly online award bonanza by sending your
Name,Add,Age,Tel to(claim_max22@9.cn )
for £891,934.00 GBP.send your data for 

more details



--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

(no subject)

[Ben Gamari]

Bcc: 
Subject: GPIO chip select support in omap2_mcspi driver

Hey,

Recently I have been looking to use a BeagleBoard to drive several
serial ADCs and DACs in a data acquisition and analysis setup. Unfortunately, the
BeagleBoard is severely limited by the number of SPI controllers it
exposes on the expansion connector (McSPI3 with 2 CS lines and McSPI4
with one). This is insufficient for our application and thus I have been
investigating adding support to the mcspi driver for using GPIO lines as
chip select lines, as is done in the pxa2xx, bfin5xx, and s3c24xx drivers.

To this end, I have a few questions about how this support was
implemented. First, it seems that the s3c24xx driver is built on the
spi_bitbang driver, despite interfacing with a dedicated hardware SPI
controller.  What is the reason for this? Was this done specifically for
the purpose of incorporating support for GPIO CS pins?

It seems like the rough idea is to add a cs_gpio field to the device
struct (omap2_mcspi) and add the appropriate code to the
omap2_mcspi_force_cs() to bring cs_gpio high or low if it is valid. The
potential problem I can see with this is that omap2_mcspi_set_enable()
is called to enable the channel before the force_cs() is called (in
omap2_mcspi_work()). If I'm interpreting the documentation correctly,
the enable bit starts the clocks, meaning that the chip will begin
clocking out data before CS is brought high. I must be missing something
here, no?

For reference, I included a short list of relevant commits below, largely for
my own benefit. I would greatly appreciate any feedback you might have.

Thanks,
- Ben


pxa2xx_spi: a7bb3909b3293d503211d7f6af8ed62c1644b686
bfin_spi: 42c78b2bf51bafb4cfa98dfecc28dd9b8bcd04b0

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev

Re: (no subject)

[Ben Dooks]

Ben Gamari wrote:
> Bcc: 
> Subject: GPIO chip select support in omap2_mcspi driver
> 
> Hey,
> 
> Recently I have been looking to use a BeagleBoard to drive several
> serial ADCs and DACs in a data acquisition and analysis setup. Unfortunately, the
> BeagleBoard is severely limited by the number of SPI controllers it
> exposes on the expansion connector (McSPI3 with 2 CS lines and McSPI4
> with one). This is insufficient for our application and thus I have been
> investigating adding support to the mcspi driver for using GPIO lines as
> chip select lines, as is done in the pxa2xx, bfin5xx, and s3c24xx drivers.
> 
> To this end, I have a few questions about how this support was
> implemented. First, it seems that the s3c24xx driver is built on the
> spi_bitbang driver, despite interfacing with a dedicated hardware SPI
> controller.  What is the reason for this? Was this done specifically for
> the purpose of incorporating support for GPIO CS pins?

The spi_bitbang driver also has a really useful spi queue and workqueue
built into it, which is what the s3c24xx spi driver actually bothers to
use.

> It seems like the rough idea is to add a cs_gpio field to the device
> struct (omap2_mcspi) and add the appropriate code to the
> omap2_mcspi_force_cs() to bring cs_gpio high or low if it is valid. The
> potential problem I can see with this is that omap2_mcspi_set_enable()
> is called to enable the channel before the force_cs() is called (in
> omap2_mcspi_work()). If I'm interpreting the documentation correctly,
> the enable bit starts the clocks, meaning that the chip will begin
> clocking out data before CS is brought high. I must be missing something
> here, no?
> 
> For reference, I included a short list of relevant commits below, largely for
> my own benefit. I would greatly appreciate any feedback you might have.
> 
> Thanks,
> - Ben
> 
> 
> pxa2xx_spi: a7bb3909b3293d503211d7f6af8ed62c1644b686
> bfin_spi: 42c78b2bf51bafb4cfa98dfecc28dd9b8bcd04b0


------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev

(no subject)

[©2011.Coca-Cola Great Britain]

-- 
04-06-20011
Your Mail-ID has been awarded 750,000.00 GBP From The Coca-Cola Online
Bonanza 2011. For claims send
Name:
Address:
Phone No:
Age: Sex:
Occupation:
Country:
Contact: Mr. Jim Gardner
Claims department : jim-gardner.c@live.com
TEL: +44 755 284 8328