one solution is say an intersection table holding the item details as say..
itemID 'fk to the tiem in question
type' either FK or 'just the type eg: "IMIE" or "Build Spec"
details eg "3.2GHZ, 2GB memory"
for a PC there could say be a raft of categories
eg
Processor: 3.2GHz Intel Prescott
Memory: 2GB
OS: Windows Xp
etc....
you may want to structure what sort of headings / details types you can have for any one device, and you may want to build in some form of explicit checking to make sure that key data is defined
an alternative is to spawn different sub tables for each distinct table type.
The former is more elegant, but a pain to ensure cdonsistency the later is easier to ensure consistency (eg a computer MUST have an OS, a processor, memory, a moby must have an IMEI)... but a pain in terms of maintenance ...although you can get round that by considering using something like XML in a generic notes field
eg
<Computer>
<type>desktop</type>
<Proc>3.2Ghz</Proc>
<OS>Windows XP</OS>
</Computer>
you may need soem form of templating to identify waht information is rrequired or optional
eg
<Mobile Phone>
<Make>Reguired</Make)
<Model>Required</Model>
<IMIE>Required</IMIE>
<colour>Optional</Colour>
<Camera>Optional</Camera>
</Mobile Phone>
<Computer>
<type>Required</type> 'or you could even break it down into allowed values eg desktop:laptop

ortable
<CPU>....blah blah