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: Kevin Somervill<kevin.m.somervill@n...>
    Date: Tue Nov 21 14:58:26 CET 2006
    Subject: [oc] Suggested extension to wishbone bus
    Top
    Hello,

    | From: cores-bounces@o...

    | I've been thinking about extending the Wishbone bus.
    |
    | The extension, called Wishbone Duplex, features separate
    | read/write sections;
    <snip>
    | As you can see 'wb_we_i' has been removed, as it's not
    | required anymore.
    |
    | Wishbone Duplex is an extension to the Wishbone standard. A
    | Wishbone Duplex core can be connected to a Wishbone Classic
    | or Wishbone RevB.3 bus using a simple wrapper.

    | Any ideas/suggestions?

    What is the expected benefit of doing this? I can see splitting out just
    the rd and wr lines as wb_re_i and wb_we_i, but I don't see the value in
    splitting out all of interface ports. It doesn't seem simplify the
    interconnect or improve performance that I can see. It's also somewhat of a
    divergence from standard interfaces with rd/wr lines. What exactly are you
    trying to address with the extension?

    Thanks,
    ./ks


    ReferenceAuthor
    [oc] Suggested extension to wishbone busRichard Herveille

    Follow upAuthor
    [oc] Suggested extension to wishbone busRichard Herveille

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