kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #98716
Re: [Bug 312380] Re: Support Intel Turbo Memory as a block device
Wow. Cool. :)
tbegush@xxxxxxxxx
623-777-9693
On Sun, Jan 11, 2015 at 3:15 PM, Erik Ekman <erik@xxxxxxx> wrote:
> If anyone still cares about this, I have done some work on a
> reverse-engineered driver.
> Reading and writing to the flash partially works, but as a raw flash
> device (MTD), not a block device. The device does not have a flash
> translation layer like an SSD.
>
> The code is available at https://github.com/yarrick/turbomem
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/312380
>
> Title:
> Support Intel Turbo Memory as a block device
>
> Status in The Linux Kernel:
> New
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> I have a Lenovo T61 (and another Lenovo T61p) that has Intel Turbo
> Memory in it. I'm not suggesting any approach as to how to use the
> memory - I just want access to it as a block device so I can do
> something with it.
>
> There is a Brainstorm entry about using Turbo Memory in a fashion
> similar to ReadyBoost: http://brainstorm.ubuntu.com/idea/12409/ This
> is *not* what this bug is about - it's just about making the device
> available for use.
>
> Here's the relevant output form lspci -vv:
>
> 02:00.0 Memory controller: Intel Corporation Turbo Memory Controller
> (rev 01)
> Subsystem: Intel Corporation Turbo Memory Controller
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 11
> Region 0: Memory at dbdffc00 (32-bit, non-prefetchable) [size=1K]
> Region 2: I/O ports at 2000 [size=128]
> [virtual] Expansion ROM at dfe00000 [disabled] [size=64K]
> Capabilities: [48] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [50] Message Signalled Interrupts: Mask- 64bit-
> Queue=0/0 Enable-
> Address: 00000000 Data: 0000
> Capabilities: [68] Express (v1) Legacy Endpoint, MSI 01
> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
> unlimited, L1 unlimited
> ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
> Unsupported-
> RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
> MaxPayload 128 bytes, MaxReadReq 512 bytes
> DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
> TransPend-
> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
> Latency L0 <512ns, L1 <32us
> ClockPM- Suprise- LLActRep- BwNot-
> LnkCtl: ASPM L0s Enabled; RCB 128 bytes Disabled- Retrain-
> CommClk+
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
> DLActive- BWMgmt- ABWMgmt-
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/312380/+subscriptions
>
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/312380
Title:
Support Intel Turbo Memory as a block device
Status in The Linux Kernel:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a Lenovo T61 (and another Lenovo T61p) that has Intel Turbo
Memory in it. I'm not suggesting any approach as to how to use the
memory - I just want access to it as a block device so I can do
something with it.
There is a Brainstorm entry about using Turbo Memory in a fashion
similar to ReadyBoost: http://brainstorm.ubuntu.com/idea/12409/ This
is *not* what this bug is about - it's just about making the device
available for use.
Here's the relevant output form lspci -vv:
02:00.0 Memory controller: Intel Corporation Turbo Memory Controller (rev 01)
Subsystem: Intel Corporation Turbo Memory Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at dbdffc00 (32-bit, non-prefetchable) [size=1K]
Region 2: I/O ports at 2000 [size=128]
[virtual] Expansion ROM at dfe00000 [disabled] [size=64K]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Address: 00000000 Data: 0000
Capabilities: [68] Express (v1) Legacy Endpoint, MSI 01
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <32us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM L0s Enabled; RCB 128 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/312380/+subscriptions
References