LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Sponsors
  • Mirrors
  • Logos
  • Contact us
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Cores > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: Miha Dolenc<mihad@o...>
    Date: Tue Nov 21 17:12:24 CET 2006
    Subject: [oc] Suggested extension to wishbone bus
    Top
    Hi all!

    One thought below.

    ----- Original Message -----
    From: "Richard Herveille" <richard@h...>
    To: <kevin.m.somervill@n...>; "'Discussion list about free open source
    IP cores'" <cores@o...>
    Sent: Tuesday, November 21, 2006 4:31 PM
    Subject: RE: [oc] Suggested extension to wishbone bus


    >
    > How do you figure it increases performance? If device A is reading device
    > B, can device C also write to it?
    > [rih] That's the basic idea

    You can implement one wishbone classic interface for reading and one for
    writing in device
    B. DAT_I and DAT_O signals are optional, so it should be allowed. Than it is
    up to interconnect
    to allow simultaneous access to both ports.

    Regards,
    Miha Dolenc

    >
    > Not many cores support concurrent access
    > [rih] Fully agreed, therefore most cores will be non Wishbone Duplex core.
    > But those few that benefit from the enhanced bus structure can use it.
    >
    >
    > nor do typical bus structures. Are you implying a cross bar type
    > functionality where device C would write to device D while A is reading B?
    > [rih] That's up to the system architect. Wishbone does not specify the bus
    > interconnect. It merely specifies the basic bus architecture.
    > What kind of interconnect (x-bar, mux, ...) is used is up to the system
    > architect.
    >
    >
    > Richard
    >
    >
    > _______________________________________________
    > http://www.opencores.org/mailman/listinfo/cores
    >
    > __________ NOD32 1875 (20061121) Information __________
    >
    > This message was checked by NOD32 antivirus system.
    > http://www.eset.com
    >
    >


     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.