[Ns-bugs] [Bug 917] Transmission power level cannot be changed (value is hard-coded to 0)
code at nsnam.ece.gatech.edu
Wed Jul 21 10:26:19 PDT 2010
--- Comment #6 from Tom Henderson <tomh at tomh.org> 2010-07-21 13:26:17 EDT ---
(In reply to comment #5)
> (In reply to comment #4)
> > Nicola, how does this relate to the goal of aligning the phy/mac interface
> > between WifiMac and SpectrumPhy? I see that spectrum devices do not pass a
> > transmit power across the boundary; e.g.
> > HalfDuplexIdealPhy::StartTx (Ptr<Packet> p)
> I think that it does not matter: for example, the idea that I had in mind for
> interfacing SpectrumPhy with WifiMac was to interpose a dedicated
> implementation of WifiPhy that used the phy/mac interface to talk to
> SpectrumPhy. This way, the WifiMac/WifiPhy interface does not need to be
The issue I see is that if we retain the per-packet transmit power setting,
spectrum Phy will need to handle it properly. If the underlying SpectrumPhy
models that will be bolted to this convergence layer can handle per-packet
txPower settings, then I think it won't matter either way.
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the Ns-bugs